Question 1

What Stord data can Polytomic sync?

Accepted Answer

Twenty six objects covering the whole operation: sales, purchase and transfer orders, inbounds and outbounds, delivery tracking, shipment and receipt confirmations, returns and returns facilities, facility balances, network overview, qualifiers tracking, inventory adjustments, bundle availability, reason codes, products, items, bundles, facilities, channels, service methods, service levels, shipment types, and billing accounts and invoices. Two naming notes: there is no object literally called Warehouses or a generic Shipments object. Warehouse data comes through facilities and facility balances, and shipment data through confirmations, delivery tracking, and shipment types.

Question 2

Which Stord objects sync incrementally?

Accepted Answer

Twelve of the twenty six, and the mechanism varies because Stord's endpoints do. Sales, purchase, and transfer orders filter on updated time, but since Stord returns them ordered by insertion rather than update, Polytomic checkpoints at the sync start and relies on deduplication for the overlap. Delivery tracking, items, and invoices filter and sort on update time so the checkpoint can advance from the last record. Inbounds, outbounds, and returns are creation time only. Confirmations filter on processed time. The remaining fourteen objects are read in full on every ETL run, which is fine given most are reference data.

Question 3

Will changes to an existing order be picked up?

Accepted Answer

It depends on the object, and this is the detail worth planning around. Sales, purchase, and transfer orders filter on update time, so edits do flow through. Inbounds, outbounds, and returns filter on creation time only, which means a record modified after it was created will not reappear in an incremental run. Returns additionally use a date level rather than timestamp level watermark, producing intentional overlap. If your reporting depends on late status changes to those objects, run a periodic full resync alongside the incremental schedule.

Question 4

Why are some shipment confirmations missing?

Accepted Answer

Shipment and receipt confirmations are filtered to records Stord has marked as processed, and that filter applies to full reads as well as incremental ones. So a confirmation that exists but has not finished processing will not appear yet; it arrives on a later sync once its status advances. That is deliberate rather than a gap, since an unprocessed confirmation is not yet a reliable record of what shipped, but it does mean a near real time count will lag slightly behind Stord's own view.

Question 5

Why move Stord data into a data warehouse?

Accepted Answer

Because fulfillment economics only make sense next to commercial data. What an order actually costs to ship against its margin, whether a facility's speed affects repeat purchase, and which products drive return costs are all joins between Stord, your ecommerce platform, and your finance system. Stord sees the operation but not the revenue. Running ETL into your data warehouse makes those joins possible, and reverse ETL on the same platform can push fulfillment status back into the CRM or support tool where customer conversations happen.

Stord

Perfect pairings

Full operations coverage

Incremental where it counts

Inventory visibility

Example workflows

What you can sync

From Stord

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Stord in minutes

More integrations beyond Stord