How do cancellations, shipments, inventory, and supply shipments sync between Endless and MasonHub?

Endless asks MasonHub to cancel fulfillment orders, checks MasonHub for shipments and cancellations every 15 minutes, pulls inventory every 15 minutes, and sends supply shipments as inbound shipments.

When you cancel or revert an In Progress fulfillment order, Endless sends MasonHub a cancel request. “Order cancellation was unsuccessful for order with external_id,” followed by the order’s ID and MasonHub’s reason, means MasonHub refused. Ask MasonHub to cancel its copy. When MasonHub cancels an order itself, Endless marks the fulfillment order Failed with “Order canceled in MasonHub.”

Leave the three “Subscribe to webhooks for” settings under Events at their defaults. Shipments and inventory reach Endless through its scheduled checks and the Actions menu. Contact Endless support to discuss realtime updates.

Endless pulls inventory every 15 minutes for each building whose inventory source is the MasonHub integration. “Pull Inventory” on the Actions menu pulls now. Units MasonHub reports as available or kit-to-ship available, plus the units Endless has allocated in that building, become the building’s Default Available location. Endless sets Default Unavailable to 0 and skips SKUs that do not exist in Endless.

Sending a supply shipment creates a MasonHub inbound shipment. It uses the supply shipment number as its identifier and purchase order name, the expected arrival date, the MasonHub location connected to the destination building, and each line’s SKU and quantity. The supply shipment needs an expected arrival date, and its products must already exist in MasonHub.

When MasonHub receives a supply shipment, receive it in Endless yourself. The next inventory pull brings in MasonHub’s new available quantities. Contact Endless support to discuss updating supply shipments from MasonHub.