Holisol

Holisol Logistics is an Indian 3PL and supply chain services company that designs, sets up and runs fulfilment centres for brands, and sells its own software to run them: a warehouse management system, a transport management system, a returnable packaging tracker and an analytics product called Verdis. It has more than 35 fulfilment centres across India and works across fashion and lifestyle, e-commerce, healthcare, automotive, luxury and FMCG. For a commerce database the finding is short: Holisol publishes no API documentation of any kind. There is no developer portal, no API reference, no Postman collection, no SDK and no public integration guide. The WMS exists as a login only web application. Integration with Holisol is agreed inside the contract, which means the specification is something to demand during onboarding rather than something to read.

At a glance

What it is

Holisol Logistics Private Limited is a Delhi NCR headquartered supply chain services company, positioned as a design, implement and manage partner rather than a pure warehouse operator. Its own description leans on the founders' combined experience and on patents filed for supply chain innovations, and it names vertical specialisations in retail, automotive, industrial and pharmaceutical.

The services that matter here:

• Multi-channel fulfilment. Holisol claims a network of more than 35 fulfilment centres across India and says it can stand up a fully functional multi-channel fulfilment centre in 30 to 45 days. Facility types named on its network page are DFC for a dedicated fulfilment centre, PUC for a pick up centre, PAS for packaging and automotive supply chain, and LMD for last mile delivery.
• Inbound and outbound supply chain, first mile, surface, air and sea freight, and cross border.
• Returnable packaging, which is a distinct business with its own tracking product.
• Consulting and feasibility studies, including warehouse site selection and layout design.

Its four named software products:

For the unified model Holisol is a fulfilment provider: where it runs a brand's operations it is the source of inventory and locations of type fulfilment_centre, and of the fulfilment side of orders, shipments and returns. It is never a sales channel, so there are no listings.

API access

There is no public route to credentials or documentation. What was checked on 2026-09-22:

1. holisollogistics.com was fetched in full and every internal link enumerated. The site's sections are about, network, solutions (consulting, fulfilment centres, hyperlocal, inbound and outbound, transportation, IT solutions), knowledge centre, careers and contact. There is no developers, API, integrations or partners technical page.
2. docs.holisollogistics.com, api.holisollogistics.com, developer.holisollogistics.com, verdis.holisollogistics.com and track.holisollogistics.com do not resolve in DNS.
3. wms.holisollogistics.com resolves and answers HTTP 200 with a login form titled "WMS Holisol Logistics". Its form targets /login and /password/email, which is the standard authentication routing of a PHP Laravel application. No API path, no documentation link and no OpenAPI file is exposed.
4. The public Postman index has no Holisol collection.
5. Public code search surfaced no customer facing Holisol API. The only developer documentation under a Holisol linked account concerns an unrelated internal knowledge portal project, with nothing about warehousing, inventory or orders.

The practical consequence: a Holisol connector is a contract deliverable. During onboarding, ask for the interface specification, a test environment, a sample of every object, and a named technical contact, and treat the absence of any of those as a schedule risk rather than a detail.

Authentication

Not published. The customer facing WMS is an email and password web login. Whether a contracted integration reuses those credentials, issues a token, or uses SFTP keys is unknown and should not be guessed at in code.

Questions to settle in writing:

• is the interface REST, SOAP or file transfer, and over which transport
• is there a UAT environment and a separate credential
• is the credential per brand, per fulfilment centre or per user
• who rotates it and on what notice

Objects we can read

Nothing through a public API. This section records what the systems demonstrably hold, so the onboarding conversation can ask for each by name.

• Inventory. Stock by SKU by fulfilment centre, with good and damaged segregation, is the core of any WMS and is the highest value object here. Ask whether you receive a snapshot or a movements ledger, and at what cadence.
• Inbound receipts. Advised versus received quantity, shortage and overage against your consignment, and the receipt document.
• Orders and their fulfilment status. Allocated, picked, packed and dispatched states, and the fulfilment centre that handled each order.
• Shipments. Holisol runs last mile itself in some geographies and hands to carriers elsewhere, so ask which waybill you will receive and whose tracking applies. Where a third party carrier moves the parcel, the carrier connectors in this catalogue are the better data source.
• Returns. Receipt at the centre, inspection outcome and restocking.
• Packaging assets. ULMS tracks returnable packaging, which is unusual and worth asking about if reusable crates or bins are part of the commercial deal.
• Analytics. Verdis is the reporting layer. A Verdis export may be easier to obtain than a transactional feed, and it is worth asking whether it can be scheduled to a file drop.
• Fees. Storage, handling and transport are contract priced and arrive as invoices. There is no settlement object.

Writing back: listings, price and stock

Not applicable as a sales channel, and undocumented as a fulfilment interface. The two writes needed are the inbound advice and the outbound order release, and neither has a published endpoint. The manual route is the WMS web application, which is where a brand's operations team works today. Assume file based exchange until Holisol says otherwise, and specify the file format, the delivery window, the acknowledgement and the discrepancy report in the contract.

Webhooks and notifications

None published. No event list, no subscription endpoint, no signature scheme.

If you end up on files or polling, plan for: a daily stock file before your storefront's morning sync, an inbound receipt file per consignment, an order status file per dispatch cycle, and carrier tracking taken from the carrier rather than from Holisol.

Rate limits and pagination

Not published, and not applicable until an interface exists. If a REST interface is offered, get the limits in the specification rather than discovering them in production.

Mapping to the unified model

No field names are published, so this is a checklist for onboarding rather than a specification.

Gaps and open questions

• Whether any API exists for clients. Nothing public distinguishes a Holisol client who gets REST endpoints from one who gets a spreadsheet. Ask directly and early.
• Whether the WMS has an undocumented API. The application is a conventional PHP stack, so it almost certainly has internal endpoints. They are not documented, not supported and not safe to build on without written agreement.
• Verdis as a data source. An analytics product with scheduled exports may be the fastest path to usable data. Untested.
• Network figures. The 35 or more fulfilment centres claim and the 30 to 45 day set up claim are from Holisol's own pages, undated. Do not quote either without both a date and a source.
• Carrier ownership. Whether the parcel moves on a Holisol waybill or a third party carrier's changes which connector supplies shipments.

Sources

• holisollogistics.com, the home page, fetched and its full internal link set enumerated on 2026-09-22
• holisollogistics.com/it-solution, the IT Solutions page, source of the WMS, TMS, ULMS and Verdis product descriptions
• holisollogistics.com/multi-channel-retail, the fulfilment centres page, source of the 35 or more centres figure and the 30 to 45 day set up claim
• holisollogistics.com/our-network, source of the DFC, PUC, PAS and LMD facility types
• https://wms.holisollogistics.com/, checked live on 2026-09-22: HTTP 200, login only application with /login and /password/email form targets
• DNS checks on 2026-09-22: docs., api., developer., verdis. and track.holisollogistics.com do not resolve
• The public Postman index and public code search, both checked for a Holisol API on 2026-09-22 with no customer facing result