Skip to main content

Overview

After an order is created in OpenBorder, updates are expected as it progresses through fulfillment. These updates, such as shipment events, customer detail corrections, or cancellations, keep OpenBorder’s OMS aligned with your commerce platform and ensure accurate order, shipment, and product-level data throughout the fulfillment lifecycle. All order updates are made by calling the Update an Order endpoint.

Common Update Workflows

1

Mark an Order as Fulfilled

Once an order has been packed, labeled, and handed off to the carrier, your system should notify OpenBorder that the order (or a specific shipment within it) has been fulfilled and is now in transit.Each fulfillment update should include:
  • The identifiers for the order (source_reference) and shipment (shipment_id) being fulfilled.
  • The shipment’s status set to fulfilled.
  • A fulfillments array containing tracking details, carrier information, timestamps, and item references.
  • The shipping_rate_id and shipping_rate of the shipment being fulfilled.
Endpoint: PUT https://api.openborder.com/api/direct/v1/orders
A 204 No Content response indicates the shipment update was successfully received and processed by OpenBorder.
2

Cancel an Order

If an order is cancelled, send an update to OpenBorder to indicate the order will not proceed to fulfillment or shipment. A cancellation update should include:
  • The identifiers for the order (source_reference) and shipment (shipment_id) being fulfilled.
  • The shipment-level status set to cancelled.
  • The shipping_rate_id and shipping_rate of the shipment being cancelled
Endpoint: PUT https://api.openborder.com/api/direct/v1/orders
Once cancelled, the shipment will no longer proceed through the OpenBorder fulfillment workflow.

Summary

All order updates are submitted using the Update Order endpoint.For detailed request parameters and the complete schema, see the Update Order API Reference.