Prozo is an Indian supply chain company that sells warehousing, freight and the software to run both: ProWMS for the warehouse, ProOMS for orders across channels, a freight management system for carriers, and a Control Tower for exceptions. It claims more than 50 warehouses, 30 or more logistics partners and 120 or more enterprise brands. For a connector the finding is that none of this is publicly documented: there is no developer portal, no published API reference, no Postman collection and no SDK. What Prozo does state, repeatedly and usefully, is the shape of an integration: API mode, FTP flat file mode, or a custom connector, scoped per brand with a stated timeline of roughly 15 to 45 days. A live first party API host exists and answers, which tells us the technology but not the contract.
At a glance
What it is
Prozo describes itself as a supply chain operating system for quick commerce and omnichannel brands, and it sells three things together.
Warehousing, in four commercial shapes: shared, dedicated, managed and on-demand, plus 4PL aggregation where Prozo manages other providers. Logistics: surface and air, same day and next day, metro express, part and less than truckload freight, appointment based deliveries, hyperlocal and dedicated milk run vehicles. Value added services: pick pack and ship, packaging and labelling, kitting and assembly, and returns processing.
The platform is the part that matters for a connector, and it is organised as four products:
Published scale, from Prozo's own pages on 2026-09-22: more than 50 warehouses pan-India, more than 30 logistics partners, more than 120 enterprise brands, and claims of 99.9 percent inventory accuracy and 2.5 times faster fulfilment. Treat all of these as vendor figures.
ProWMS's inbound layer is described in operational detail that is worth recording, because it tells you which objects should exist behind whatever interface you are eventually given: gate entry validation, scan based GRN, barcode generation, quality check workflows, handheld terminal putaway with automated putaway recommendations, and label generation. Inventory governance adds FIFO and FEFO shelf life management, good and damaged segregation at receipt, bin level and SKU level cycle counting with live discrepancy tracking, and full audit trails.
For the unified model Prozo is a 3PL and an order management system: inventory with a real location dimension, orders, shipments, returns and locations. It is not a sales channel, so there are no listings.
API access
There is no public route. What was checked on 2026-09-22:
docs.prozo.comanddeveloper.prozo.comdo not resolve.https://www.prozo.com/api-docsreturns HTTP 403, so a path exists but is not served publicly.https://api.prozo.com/returns HTTP 200 with a Spring Data REST style HAL document whose_linksarecities,countries,schedulerJobInfoes,userMasters,usersandprofile. These are platform utility resources, not commerce objects: no orders, no inventory, no consignments are exposed at the root.https://api.prozo.com/profile, which in a Spring Data REST application is the metadata endpoint, returns HTTP 401 with{"subCode":7000,"message":"Invalid credentials or token"}. So the API is real, authenticated, and its error envelope is custom rather than the Spring default.- The public Postman index has no Prozo collection. Searches return only the unrelated Ukrainian procurement platform Prozorro.
- No first party OpenAPI file or SDK was found in public code search.
What Prozo does publish is the integration model, and it is specific enough to plan against. ProOMS is said to integrate natively with Shopify, WooCommerce, Magento, Dukaan and OpenCart, and for a custom storefront "Prozo's open API framework enables full integration within 15 to 30 days". ERP integration is offered in three modes with published timelines:
Prozo also names the aggregators and order management systems it bridges to rather than replaces: Unicommerce, Vinculum, EasyEcom, Browntape, Orderhive and Eshopbox, described as API based bridges for order sync, inventory push and returns reconciliation. If a brand already runs one of those, the cheapest connector is to that system, not to Prozo. For Eshopbox in particular, see /connectors/eshopbox, which has a fully public API.
Authentication
Not published. The one verified fact is the 401 error envelope above, which shows a token or credential check on api.prozo.com and a custom subCode in the body. Nothing about obtaining, scoping or refreshing a credential is public. Do not design a credential store from this; get it in writing during onboarding, and ask specifically whether the credential is per brand, per warehouse or per channel.
Objects we can read
Nothing is readable without a contract, so this section records what the product demonstrably holds, so you know what to ask for by name.
Orders
ProOMS holds marketplace, webstore and B2B orders in one place with unified status tracking, routed across fulfilment centres. Ask for: the order object with its item lines, the channel identifier, the status vocabulary including the warehouse states, and an incremental read keyed on an updated timestamp.
Inventory
The strongest asset and the thing to prioritise. Prozo advertises a single inventory pool across channels, warehouses and fulfilment nodes, with bin level and SKU level counts, good and damaged segregation, FIFO and FEFO shelf life tracking and cycle count discrepancies. Ask for: stock by SKU by warehouse with separate sellable, reserved, damaged and inbound buckets, a movements ledger rather than only a snapshot, and batch or expiry attributes where shelf life is managed.
Inbound receipts
ProWMS records gate entry, scan based GRN, quality check outcome and putaway. Ask for: the consignment object, its advised versus received quantities, shortage and overage, and the putaway completion event.
Shipments and tracking
Courier allocation through the PACE engine, NDR and NPR management, and delivery status push-back to storefronts. Ask for: the shipment with its carrier and waybill, the scan history, and whether Prozo can push status to your endpoint rather than only to a storefront connector.
Returns
Returns processing is a named ProWMS layer, with gate entry to disposition tracked as an SLA. Ask for: the return object, the disposition outcome, and whether restocked units reappear in the sellable bucket with a traceable event.
Payments and settlements
Nothing published. Storage, handling and freight are contract priced. Expect invoices, not an API.
Writing back: listings, price and stock
Prozo is not a sales channel, so there are no listings and no prices to write. The two writes a fulfilment integration needs are the inbound advice and the outbound order release, and both exist in the product but have no published interface.
Practically, there are three routes, in descending order of preference:
- API mode. Prozo says its API framework can integrate a custom storefront in 15 to 30 days. Ask for the specification, a UAT credential and a sample request and response for each object before committing to a timeline.
- FTP flat file mode. Explicitly offered for SAP and Oracle. This is a scheduled file drop, so design for a batch window, a file naming convention, an acknowledgement file and a reconciliation report. Slower, but usually available sooner.
- Custom connector. Prozo builds it. You own nothing and change requests go through their team.
The manual fallback is the WMS and Control Tower logins on the Prozo site, which are operational screens with exports.
Webhooks and notifications
Not published. Prozo's copy mentions near real time sync and delivery status push-back for storefront integrations, so a push mechanism exists inside its own connectors, but there is no public event list, no subscription endpoint and no signature scheme.
If you end up on file or polling mode, this cadence matches the operational rhythm Prozo describes:
Rate limits and pagination
Not published. The HAL root exposes templated links of the form {?page,size,sort}, which is the standard Spring Data REST pagination contract, so if the contracted API is the same application expect page, size and sort parameters and a _embedded plus page envelope. That is an inference from the technology, not a documented behaviour, and it should be confirmed rather than assumed.
Mapping to the unified model
No field names are published, so this table maps unified fields onto the concepts Prozo names and is a checklist for the onboarding conversation rather than a specification.
Gaps and open questions
- Everything on the read and write side. No endpoint, field, authentication flow or event is published. The page's confidence is high only on the absence of documentation.
- What
api.prozo.comactually serves. The root exposes utility resources and the metadata endpoint is authenticated. Whether the contracted commerce API is the same application, under the same host, is unverified. - Whether API mode is offered to every brand. The FTP flat file mode is named for the large ERPs, which suggests files are the default for enterprise work. A smaller brand may be offered only a connector.
- Push versus poll. Near real time sync is claimed for storefronts. Whether Prozo will push to an arbitrary endpoint you control is the single highest value question to ask.
- Bin level exposure. ProWMS tracks bin level stock internally. Most 3PL interfaces collapse this to site level. Confirm before promising bin analytics.
- The 403 on
prozo.com/api-docs. A documentation path exists and is closed. Ask whether it can be opened, or a copy shared, during evaluation rather than after signature. - Vendor figures. Warehouse count, brand count and accuracy percentages are all self published with no date. Do not quote them without both.
Sources
- prozo.com, the home page, for the solution list and the platform structure
- prozo.com/technology/order-management-system, for ProOMS, the 50 or more channel claim, the named storefront and aggregator integrations, the ERP integration modes and their stated timelines, and the 120 or more brands and 50 or more warehouses figures
- prozo.com/technology/warehouse-management-system, for the six ProWMS layers and the inbound, inventory governance, cycle count and returns capability lists
https://api.prozo.com/, checked live on 2026-09-22: HTTP 200 with a HAL index whose links arecities,countries,schedulerJobInfoes,userMasters,usersandprofilehttps://api.prozo.com/profile, checked live: HTTP 401 with{"subCode":7000,"message":"Invalid credentials or token"}https://www.prozo.com/api-docs, checked live: HTTP 403.docs.prozo.comanddeveloper.prozo.comdo not resolve- The public Postman index, searched for Prozo collections on 2026-09-22: no first party collection exists
- /connectors/eshopbox, the alternative route for brands whose stock is coordinated through Eshopbox, which does publish an API