Integrations

The same ShipperOne API is consumed in different sequences by different kinds of integrators. These guides walk through the flow per role — what endpoints to call, in what order, and with which payloads.

Roles covered

• ERP integration — for finance / ERP systems that drive allocation and invoicing (and, optionally, returns). Polls pending_allocation and pending_invoice; calls allocate and invoice. Does not handle physical shipment.

• Fulfillment partner integration — for any party that physically fulfils orders: 3PLs, dropshippers, or in-house warehouses (often running a WMS). Polls pending_accept and pending_shipment; calls accept, reject, and ship.

Fulfillment order lifecycle

A fulfillment order is a unit of work produced by ShipperOne when a customer order is routed to a location. It progresses through four stages, each with its own polling endpoint and a matching action endpoint that moves the order forward:

#	Stage	What happens	Polling endpoint	Action endpoint	Owner
1	Pending accept	Warehouse decides if it can fulfil	GET /V1/fulfillmentOrders/pending_accept	POST /V1/fulfillmentOrder/accept / …/reject	Fulfillment partner
2	Pending allocation	Stock is reserved against the order	GET /V1/fulfillmentOrders/pending_allocation	POST /V1/fulfillmentOrder/allocate	ERP
3	Pending shipment	Order is picked, packed and dispatched	GET /V1/fulfillmentOrders/pending_shipment	POST /V1/fulfillmentOrder/ship	Fulfillment partner
4	Pending invoice	Fiscal invoice is issued for shipped items	GET /V1/fulfillmentOrders/pending_invoice	POST /V1/fulfillmentOrder/invoice	ERP

Common conventions

These rules apply across both guides:

• Authentication — every request carries a Bearer token. See Authentication for details.
• Base URL — each customer runs its own ShipperOne instance; substitute your tenant hostname for YOUR_SHIPPER_BASE_URL in all examples.
• Path prefix — every REST URL is shaped https://YOUR_SHIPPER_BASE_URL/rest/{store_code}/V1/…. Your store_code is provided alongside your token — typically all on single-store tenants, or a country code (rs, hr, me, …) on multi-country tenants.
• items[] payload — every action that operates on line items takes an explicit items[] array, supporting both full and partial operations with the same payload shape. See each guide for partial-operation rules per stage.