Loqally

LoQally is not a courier. It is a dark store network that a D2C brand plugs into its own Shopify storefront to offer 2 to 4 hour delivery without listing on a quick commerce marketplace. Stock sits in LoQally operated micro-warehouses, LoQally picks, packs and runs the last mile, and the brand keeps the customer relationship and the margin. That makes it a fulfilment provider rather than a carrier, and unusually for this part of the catalogue it does hold inventory, so the inventory and locations tables genuinely apply. There is a live API host but no published documentation. This page records what is verifiable as of 2026-09-22.

At a glance

What it is

A small, young, Pune based company. The site states it was founded in October 2024, that the team is six people, and that it runs more than 10 dark stores, currently live in Delhi NCR with an ambition of 50 plus. It claims more than 50 D2C brands. Category emphasis in the testimonials is snacks, beverages and health and wellness, which fits the quick commerce basket.

The pitch is explicitly anti-marketplace: instead of listing on a quick commerce platform and paying 15 to 35 percent commission while the platform owns the customer, the brand keeps its own Shopify checkout and shows a 2 to 4 hour delivery promise on its own product page. LoQally supplies the dark store network, the picking and the last mile.

Published pricing on 2026-09-22, which is unusually transparent for this sector:

Stated operational figures are sub 6 hour delivery as standard, 4.2 hours average, and 8 days from contract to live. Those are vendor numbers.

Named integrations, from the homepage integration strip: Shopify, EasyEcom, Uniware, which is Unicommerce's warehouse product, and ClickPost. That set tells you where LoQally sits in a stack: orders arrive from Shopify or from an order management system, and tracking is normalised through ClickPost. See /connectors/shopify, /connectors/clickpost and the Unicommerce and EasyEcom pages for those interfaces, which are documented, unlike LoQally's own.

API access

No documentation exists, but an API is running. Checks on 2026-09-22:

The API host answers. GET https://api.loqally.in/health returns, without credentials:

{
  "status": "ok",
  "db": "connected",
  "uptime": 344031.679793319,
  "timestamp": "2026-09-21T20:00:11.966Z",
  "memory": { "rss": "285MB" }
}

Every other conventional path, including /, /docs, /api-docs, /swagger, /openapi.json, /v1 and /api/v1, returns a bare Express 404 reading Cannot GET /<path>. So there is a real service with a database behind it, running as a single Render instance, and it publishes no discovery document and no reference. The service name loqally-v1-0 suggests a first production version.

The route to access is the sales conversation. The stated onboarding is: day 1 a call, days 2 to 5 LoQally connects Shopify and syncs inventory, days 6 to 7 the brand and LoQally jointly define pincodes, allocate inventory and set delivery promises, day 8 onward live with support. Note what that implies: LoQally does the integration work, on their side, against the brand's Shopify. A brand is not expected to write code.

Authentication

Not published. The dashboard at loqally.in/login is a Next.js application with an email and password style login and a /register route. No API key, token endpoint, signature scheme or lifetime is described, and the Express host gives nothing away on unauthenticated paths. No code sample can be written honestly.

The Shopify side of the connection uses Shopify's own app grant, since LoQally connects to the brand's store during onboarding, and Shopify's OAuth is fully documented. That is the only part of the credential chain that can be designed today.

Objects we can read

Nothing is documented. What follows is what exists, named from first-party material, so the right questions get asked.

Orders

Orders originate in the brand's Shopify store and are routed to LoQally when the buyer's pincode is inside a served dark store catchment. LoQally is a fulfilment executor, not the system of record. Read orders from the Shopify connector.

Order items

Not separately described. The 2 rupees per item Shopify app processing charge implies per-line-item handling, so a line item concept exists internally.

Products and listings

Not applicable as listings. LoQally needs product identity and dimensions to stock a dark store, and the EasyEcom and Uniware integrations are the likely source, but it does not own or publish a catalogue.

Inventory

This is the object that makes LoQally different from every other entry in this part of the catalogue: it physically holds stock. The onboarding description says LoQally will "sync inventory" during days 2 to 5 and "allocate inventory" during days 6 to 7, and storage is billed at 0.30 rupees per unit per day, which requires a per-unit per-location count.

So a real inventory table exists behind the dashboard, keyed by SKU and dark store. Nothing about its interface is published: no endpoint, no update mechanism, no reservation model, no sample. Whether stock is pushed from the brand's order management system or pulled by LoQally is the first question to ask.

Shipments and tracking

Delivery is local and same day, so the shipment object is short lived: an order, a dark store, a rider and a delivery timestamp. The dashboard shows live delivery events, and ClickPost is a named integration, which suggests tracking is exposed to the brand in ClickPost's normalised form rather than LoQally's own. If so, read the scans from ClickPost, where the schema is documented.

There is no AWB in the courier sense, and no public tracking page was found.

Returns and cancellations

Not described in public material. The site's own SEO keywords emphasise RTO and CIR reduction, which are forward-delivery failure modes rather than returns. Whether LoQally accepts a return back into a dark store, and how that restocks, is unknown and commercially important for a brand holding inventory there.

Proof of delivery and NDR

Not described. On a 2 to 4 hour local delivery these still matter, particularly for COD orders at 20 rupees per order handling. Ask.

Payments and settlements

COD handling is a priced option, so LoQally collects cash and must remit it. No remittance cycle, statement format or interface is published anywhere. The dashboard shows a total savings figure, which is an analytics view rather than a settlement ledger.

Customers

Buyer name, address and phone travel with every order to the rider. All PII. The whole product proposition is that the brand keeps the customer relationship, so LoQally should be a processor rather than a controller of that data. Get that written into the contract.

Locations

Dark stores are the locations, more than 10 as of 2026-09-22, all in Delhi NCR, with expansion stated. A brand selects the pincodes it wants served during onboarding. No location list or serviceability endpoint is published.

Writing back: listings, price and stock

Not applicable, this is a fulfilment network and not a sales channel. LoQally holds no listings and sets no prices.

The nearest equivalent to a write path, and the one that matters operationally, is stock allocation into a dark store: deciding which SKUs sit in which location at what depth, and keeping that count in step with the brand's own inventory. The site describes this as a joint configuration exercise during onboarding rather than a self-serve operation, and publishes no mechanism for it. Whether a brand can adjust allocation continuously through the dashboard or has to ask, and whether there is any programmatic route, are the two questions that decide how usable this is at scale.

The other write-shaped operation is order routing: an order that qualifies goes to LoQally, one that does not goes to the brand's normal courier. How that decision is made, and whether a brand can override it per order, is not documented.

Webhooks and notifications

Not published. The dashboard shows a live event feed of deliveries and dark store activations, which is a UI, not a subscription.

If push is not available, the pull options are LoQally's dashboard, which has no documented interface, or ClickPost, which does. Given the integration strip names ClickPost explicitly, routing delivery events through ClickPost is the pragmatic design: poll or subscribe there, and treat LoQally as the carrier value on the shipment.

Rate limits and pagination

Not published. The API host is a single Render service with roughly 285 MB resident at the time of checking, which is a small deployment. Whatever interface is eventually granted, treat it as capacity constrained and negotiate a cadence rather than assuming headroom.

Mapping to the unified model

Field names are unknown. The table records the concepts and where the data is better read from.

Gaps and open questions

• Is there a brand-facing API at all, or is api.loqally.in purely the dashboard's own backend. This decides whether a connector is possible.
• How inventory is synced: push from the brand, pull by LoQally, or manual. And at what frequency, because a 2 to 4 hour promise on stale stock is an oversell.
• Whether returns can be accepted back into a dark store, and how that restocks.
• COD remittance cycle and statement format. Nothing is published, and COD is a priced option.
• Delivery event delivery: through ClickPost, through a LoQally interface, or dashboard only.
• No serviceability lookup. Coverage is agreed as a pincode list during onboarding, with no published way to query it.
• Scale risk. Six people, 10 dark stores, one Render instance, founded October 2024, capacity capped at three new brands a month. Every one of those is a reason to keep a fallback courier configured.
• The company's own metadata still points at a domain it no longer controls, which is a small but real signal about operational maturity.

Sources

• LoQally homepage, read 2026-09-22, for the product, company facts, dark store count, integration names, pricing table, onboarding timeline and stated metrics
• Live DNS and HTTP checks on loqally.in, www, api, app, dashboard, login and docs.loqally.in, and on loqally.com, run 2026-09-22
• GET https://api.loqally.in/health, which returns the health object quoted above, and the Express 404 responses on every other conventional path
• whois for loqally.com, showing a 2014 creation date under Unstoppable Domains and a for-sale lander, which is not the operating domain
• Internet Archive availability for loqally.com, whose most recent capture is 2025-07-12, and which holds no capture of loqally.in