Inventory
Backchannel's Inventory Engine provides a real-time, high-fidelity view of stock levels across global logistics networks, synchronized with your ERP.
Sync Life Cycle
Ingestion
Raw stock levels are pulled from ERP (SAP, Linx, Totvs) every 60 seconds.
Resolution
Stock is reconciled against active orders and pending reallocations.
Propagation
Final 'Available-to-Promise' (ATP) figures are broadcasted to all sales channels.
The Inventory Item
The atomic unit of stock management. Every unique SKU at a unique location is an Inventory Item.
Global Identifiers
| Field | Type | Description |
|---|---|---|
skuRequired | string | Stock Keeping Unit. Must match the identifier in your ERP. Example: WRA-TEX-001 |
brand_idRequired | string | The owner brand of the inventory. Example: brand_01JGK9 |
barcode | string | UPC/EAN associated with the SKU. |
Stock Metrics
| Field | Type | Description |
|---|---|---|
physical_stock | integer | Total quantity present in the warehouse shelf. |
reserved_stock | integer | Quantity already allocated to processing orders. |
available_stockRequired | integer | Net available stock (Physical - Reserved). This is the value pushed to storefronts. |
safety_stock_buffer | integer | Minimum stock level maintained before showing 'Out of Stock' flag. |
Query Inventory
GET /v1/inventoryRequest Parameters
| Field | Type | Description |
|---|---|---|
brand_idRequired | string | Filter inventory by brand owner. |
warehouse_id | string | Filter by specific logistics node. |
sku | string | Target a specific product identifier. |
Trigger Reallocation
POST /v1/inventory/reallocateProgrammatically move virtual stock between fulfillment nodes. This is typically used by the Agentic Rebalancer but can be triggered manually.
{
"sku": "WRA-TEX-001",
"from_node": "WH_SP_01",
"to_node": "WH_RJ_02",
"quantity": 500
}Bulk Operations
For enterprise brands with large catalogs, use the bulk endpoints to update inventory levels across multiple SKUs and locations in a single call.
Multi-Warehouse Mapping
BackchannelOS maps your internal ERP `warehouse_ids` to our `fulfillment_nodes`. This allows for complex routing logic like "Ship-from-Store" or "Regional Hub" prioritisation.