Warehouse Management
Warehouse Management – Dashboard
Product inventory item definitions can be manually defined through these or imported from external sources. Inventory reservations and item counts for the warehouse are automatically adjusted during order entry, placement and modifications, based on product inventory item definitions and rules.
The warehouse application generally supports the administration of facilities (warehouses, brick-and-mortar stores, manufacturing sites etc.) and the shipping of goods. All incoming and outgoing shipments can be traced and individual shipments managed. Shipping features the individual allocation of goods to shipments, split shipping, drop shipping, the creation of packing slips, route and shipment plans and more. Our shipment gateways are pre-configured to support automated cost calculation by means of external APIs. Currently the following carriers are supported: USPS, DHL, UPS, FedEx.
Warehouse management consists of a detailed warehouse management interface. It is possible to add multiple warehouses & facilities to a company. Each warehouse supports the scheduling, picking & packing and detailed inventory plan for each product down to the location sequence id. Each inventory also displays the quantity on hand and total available inventory on a per product item basis. Transfer in between facilities can be managed.
Scipio instances can be replicated to other Scipio instances through EntitySync and synchronized to externals systems using custom-written services communicated using SOAP (Apache Axis), RPC, etc. and integrated into the service architecture. It is possible to add all facilities/warehouses individually and to manage their respective stock on an item basis.
The warehouse management application contains the following functions:
- Shipment Gateway Config
- Shipment Gateway Config Types (e.g.: USPS, UPS, Fedex, DHL)
- Individual Shipment Gateway Config (API Parameters)
- Shipments
- Shipment
- Items
- Order Items
- Packages
- Route Segments
- Shipment Plan
- Shipment
- Warehouses
- Warehouse
- Warehouse Information
- Inventory
- Packing
- Picking
- Scheduling
- Settings
- Warehouse
The application in 4.0#
The warehouse manager in 4.0: the facilities, the stock per location and the shipments that leave the building.
Do it with an agent#
The warehouse ships an MCP server. Point your agent at the facility webapp and it receives, counts and ships with you.
claude mcp add --transport http scipio-facility "https://<host>/facility/mcp" --header "Authorization: Bearer <token>"Two tools carry the application. Every call names the tool and one action.
inventory—receive,get,item_update,adjust_start,count_apply,reorder_point,transfer_create,transfer_update,facility_create,facility_location_create,facility_address_set,facility_product_set.shipment—create,find,get,plan,package_add,route_update,update,label_create.
Receive a delivery#
“Fifty units of MF_FRAME arrived at the main warehouse on pallet lane A-04. Book them in.”
The agent calls inventory:receive with the facility, the product, the
quantity and the location. Ask for inventory:get afterwards to see the new
stock level.
Count a lane#
“Start a count for lane A-04, here are the numbers I read, apply them and show me the difference.”
The agent calls inventory:adjust_start, then inventory:count_apply. The
variance stays on the record, so the correction is traceable.
Pack and label#
“Plan a shipment for order WSCO10050, pack it into two parcels and print the labels.”
The agent calls shipment:plan, shipment:create, shipment:package_add
twice and shipment:label_create.
The token is a user login. The agent does what that user may do, and nothing more. Every call writes one audit row. Read the security model before you hand a token out.

