How and when does Endless record Mintsoft shipments and tracking?

Endless records a Mintsoft shipment when the order reaches a status whose external name is Despatched. A printed label or a courier record alone does not count. Mintsoft’s invoiced statuses that keep the Despatched external name also count.

Endless checks every In Progress fulfillment order sent to Mintsoft every 15 minutes, however old it is. “Pull Shipments” on the integration’s Actions menu runs the same check now.

When the warehouse splits an order, Endless follows Mintsoft’s split links from the order it sent and reads every part. Each dispatched part becomes its own shipment in Endless, with that part’s item quantities, tracking number, tracking link, courier service, and parcel count. Parts that are not yet dispatched are skipped until they are. The fulfillment order becomes Fulfilled when the shipments cover all of its items.

Endless reads and checks every part before it records anything. Each SKU Mintsoft reports must match exactly one line on the fulfillment order, and back-ordered units stop the import. When a check fails, Endless records nothing for that fulfillment order and shows the reason on its timeline and in the integration’s Activity tab. Common reasons are a SKU on two lines, a missing database time zone, or an order that belongs to a different Mintsoft client.

While the fulfillment order is In Progress, each check updates the same shipments when Mintsoft changes tracking or quantities, and unchanged data does not create new shipments. When Mintsoft cancels every part that has not shipped, Endless marks the fulfillment order Failed with “Order canceled in Mintsoft.”

Endless checks a fulfillment order until it is Fulfilled. Correct later tracking or quantity changes from Mintsoft in Endless yourself.