What can a Custom Fulfillment integration do in Endless, and which buildings and fulfillment orders does it handle?
A Custom Fulfillment integration gives your warehouse’s own system API credentials to work fulfillment orders in Endless. It can read orders and fulfillment orders, move fulfillment orders through their statuses, record shipments with tracking, adjust inventory, and receive supply shipments.
Your system reads the fulfillment orders assigned to it and marks them In Progress itself. For these fulfillment orders, “Send for fulfillment” shows “Fulfillment uses a custom fulfillment integration.” Leave Auto-advance off for the Ready to In Progress step in rules that use it. To have Endless tell your system about new work, create an automation with the Fulfillment Created or Fulfillment Ready trigger and the Send Webhook action.
To point fulfillment orders at it, select it as the building’s “Default fulfillment integration,” pick it with “Change Fulfillment Integration” on one fulfillment order, or use Set Fulfillment Integration in a Fulfillment Created automation.
Your system can read every order in the company. It can change a fulfillment order or record its shipments only while that fulfillment order is assigned to the integration and is not Canceled. When a routing strategy creates the fulfillment orders, assign them with Set Fulfillment Integration in a Fulfillment Created automation, before any Process Fulfillment action.
Your system finds out about a cancellation by reading the fulfillment order, which is now Canceled, or through the API’s order update subscriptions. Canceling a fulfillment order that is In Progress asks you to “Pull it back.”
Your system can update inventory by sending adjustments with a reason through the API.
The credentials are shown once, when you create the integration. Save them then.