Integrations
Connect warehouse work with order management, purchasing, carriers and the equipment on your floor.
Plan each connection around a clear owner and a verified operating contract. This website describes the intended integration scope. Connector availability, credentials, actions and device compatibility must be confirmed during application configuration.
- Items and inbound deliveries
- Item masterin
- Purchasing and advance shipment noticesStockMovements · in
- Production and returnsReceipts · in and out
- Orders and fulfillment
- Order managementCartons · in
- Customer shipping requirementsin and out
- Warehouse equipment
- Scanners and handheldsin and out
- Scales and printersin and out
- Conveyors and sortationin and out
- Carrier connections
- Parcel accountsin and out
- Freight shipmentsShipments · in and out
- Uncertain responsesin and out
- Finance and quality
- Financial inventoryInventory, StockEvents · in and out
- Qualityin and out
- Agents
- Your agentWorks within the permissions you assign
Items and inbound deliveries
- Item master. Bring in SKUs, units and conversions, dimensions, weights and lot or serial controls. Define which warehouse attributes are maintained locally and who supplies cost for adjustment decisions.
- Purchasing and advance shipment notices. Map expected lines and source revisions into receiving. Return confirmed receipt quantities and reviewed differences without treating later stock movements as changes to the original delivery.
- Production and returns. Reconcile production receipts and authorized customer returns with their source references. Quality disposition and financial effects remain with the systems and people assigned to those decisions.
StatusPendingLabelsReadyStaged
Orders and fulfillment
- Order management. Import demand, ship-to details, service, cutoff and holds. Retain the source order-line identity through reservations, picks and cartons. Confirm how changes or cancellations affect work already released.
- Customer shipping requirements. Configure the required shipment notices, packing documents and labels against the customer’s routing guide. Validate identifiers and label output with the receiving party before rollout.
Warehouse equipment
- Scanners and handhelds. Test task confirmation, barcode formats, user identity and repeated scans on the actual devices. A disconnected device needs an explicit recovery and reconciliation process.
- Scales and printers. Verify weight units, scale capture and label output at each pack station. Reprinting an existing label must not purchase another shipment.
- Conveyors and sortation. Where a warehouse control system is present, define the exchange of container identity, destination and movement confirmation. Equipment safety controls stay with that system.
Carrier connections
- Parcel accounts. Confirm the supported carrier or postage-provider connector, account, service and label format. Catalog setup alone does not implement a new connector.
- Freight shipments. Agree the bill-of-lading, pickup, tender and tracking exchanges required for the selected carrier. Closing the manifest freezes the batch; actual handover is a separate event.
- Uncertain responses. Keep a stable request identity. If a carrier may have accepted a request before the connection failed, reconcile that outcome before trying again. Void and reissue decisions retain their reason and links to the original label.
StatusPendingLabelsReadyStaged
Finance and quality
- Financial inventory. Agree whether each destination posts stock events or receives position snapshots. A snapshot used for reconciliation must not post quantities a second time. Quantity events, valuation ownership and the migration cutoff need a shared contract.
- Quality. Route damage and hold evidence for review. A returned disposition must pass the warehouse’s stock and authority checks before it changes availability.
How connections are governed
service accounts, audit, pausingUse scoped service identities, retained source references and per-destination delivery records. Separate local stock posting from message delivery: retrying an outbound message must not repeat the inventory effect. Confirm acknowledgments, resolve conflicts and use controlled reconciliation where a destination cannot deduplicate requests. A successful transport response alone does not prove the receiving system applied the intended business action.
The API is one more client of the same interface. AI agents →
# Example work after configuration
$ curl -fsSL erpai.studio/skill.md
› Show the orders at risk of missing today's shipping cutoff.
› List the replenishment work still open for the proposed wave.
› Compare the received quantities with this delivery's expected lines.
› Trace the movements behind this count difference.
› Find staged cartons whose label outcome is still unresolved.