Available foundation
Read collected inventory
Reading supported warehouses and inventory forms the foundation. Coverage depends on the sources actually connected.
CIAMA
CIAMA
English
In-house inventory · Outsourced logistics
Your warehouse handles some sales, a third-party logistics provider fulfils others, and Amazon FBA holds separate inventory. CIAMA brings accessible information together so your teams can locate products and follow connected operations.
Licensed software · Dedicated hosting managed by Dawap or on-premise
Amazon FBA, logistics software and fulfillment providers: accessible inventory, warehouses and operations depend on API access. Connections depend on scope or require an integration assessment. No official partnership is claimed.
View connections and availabilityOne business, several stock locations
Physical stock, sellable quantity and a dispatched parcel describe different things. Connecting them starts with the product identifiers and statuses supplied by each source.
In-house warehouse
Your system retains responsibility for preparation and physical movements. CIAMA uses the information made available through the agreed exchanges.
3PL provider
The provider runs its operations. Accessible quantities and events depend on its API, the permissions granted and the connection implemented.
Amazon FBA
Stock collected by the FBA connector is read in its own context. This does not mean that orders from every channel can already be sent to Amazon.
A shared view of connected sources, with their scope and limitations. Physical fulfilment remains with the relevant tools and operators.
From quantity to tracking
A shared view is useful when you know which decisions each piece of data supports. Explore the detail in the relevant modules.
Read collected inventory by warehouse and identify its source. Check what each quantity means and how often it is refreshed before using it.
Explore multi-warehouse visibilityDefine: product identifiers, warehouses, quantity type and collection frequency.
Choose the sources relevant to the channel. Marketplace stock updates depend on the connector and its activation; a visible quantity does not reserve units.
Understand stock synchronisationDefine: selected sources, calculation rules and destination channels.
Bring accessible shipping details and available tracking information together. Identify the carrier, logistics provider and order to interpret each status.
Explore shipment trackingDefine: tracking source, available events and refresh frequency.
Define the right automation scope
Reading a provider’s stock and sending it an order are separate flows. We check each one before including it in your project.
Available foundation
Reading supported warehouses and inventory forms the foundation. Coverage depends on the sources actually connected.
Connector-dependent
Marketplace stock updates require a compatible connector and activation. Our offering also covers inventory distribution to ecommerce stores, according to their APIs and your availability rules.
In development
The API currently supports writing stock for the default warehouse. Writing stock by external warehouse is in development, with scope to be defined for your providers.
Prepare a useful demonstration
A representative example helps check identifiers and define an initial scope without assuming that all your systems work in the same way.
Your warehouses, WMS, 3PLs, FBA accounts and carriers, along with the teams responsible for each stage.
A product reference, its identifiers, exposed quantities and a tracking example, without unnecessary personal data.
Prioritise visibility and useful flows. Document what is available, configurable or requires development, then choose the deployment.
Yes. The project can bring these sources together according to accessible data and agreed connections. Each warehouse retains its identity; preparation and update responsibilities are defined during scoping.
No. An API makes an integration worth assessing. We check access, available data and the development needed to put the exchanges in place.
No. Your WMS retains receiving, put-away, picking and packing. CIAMA brings information together to track inventory and connected operations.
Automatic allocation is outside the scope described here. Your warehouse selection rules and order transfers need to be assessed as a specific integration.
No. They illustrate the ecosystem under consideration or within the team’s expertise. Tracking, label purchases, returns and other services are separate flows, assessed individually for your project.
Tell us about your warehouses and providers. We will prepare a demonstration focused on the information and flows your teams need.
Discuss your logistics setup