What can an Operations integration do in Endless, and how is it different from a Custom Fulfillment integration?

An Operations integration gives your own tools API access to read Endless data and submit operational records. Unlike a Custom Fulfillment integration, it is not tied to buildings and fulfillment orders are never assigned to it. Endless provisions an access token, API key, and API secret. The integration does not have settings or actions, and it does not send or pull anything on a schedule; every change comes from calls your tools make.

Its default role is Operations Integration. With it, your tools can:

• read products, orders, fulfillment orders, inventory, purchase orders, shipments, customers, and most other company data;
• create and update orders, cancel and uncancel them, and record shipments;
• adjust inventory;
• create and update purchase orders, suppliers, supply shipments, booking requests, and ASNs, and receive shipments;
• create and update customers and planning records;
• request exports.

It cannot edit products; use a Custom Product Integration for that. It also cannot control internal processing, such as approving orders, allocating inventory, routing, or creating and advancing fulfillment orders, and it cannot change company setup or access permissions.

A Custom Fulfillment integration is built for a warehouse system. You choose which buildings it handles, and fulfillment orders for those buildings are assigned to it for your system to read and work. Its Fulfillment Integration role lets it allocate, mark fulfillment orders in progress or fulfilled, create shipments and carton labels, push tracking, adjust inventory, and work ASNs and receiving.

Use a Custom Fulfillment integration when the system ships orders from a building Endless should send fulfillment orders to. Use an Operations integration when a tool needs to read data or submit orders, purchasing records, stock adjustments, or shipment reports without being the building’s warehouse system.