AAJ Enterprise

AAJ Enterprise (AAJ Supply Chain Management): a 1 Mn sq ft Indian 3PL whose WMS claims an open API but publishes no spec, portal login only.

AAJ Enterprise is the older trading name of AAJ Supply Chain Management Pvt. Ltd., an Indian third party logistics operator that stores stock for brands, fulfils marketplace and D2C orders from it, processes returns and moves the parcels through its own transport arm. The name in our catalogue resolves there: aajenterprise.in redirects to aajenterprises.com, which redirects to www.aajscm.com. The transport arm, AAJ Swift, is documented separately at /connectors/aaj-swift and is not restated here. This page covers the warehousing and fulfilment surface: inbound receipt, stock by warehouse, outbound order release, returns processing and the client reporting layer. AAJ markets "60+ platform integrations" and an "Open API", but publishes no specification, no developer portal and no sample request, so every field below is either observed or explicitly marked as unpublished.

At a glance

Note

Two AAJ hosts answer but neither is developer documentation. wms.aajscm.com is the client warehouse application, and its page title is "WMSOnWeb", which points at a licensed .NET web product rather than the wholly in house build the marketing pages describe. docs.aajscm.com is an internal document review portal behind Microsoft sign in, for reviewing AAJ's own module documents, not an API reference.

What it is

AAJ Supply Chain Management Pvt. Ltd. is a pan India 3PL headquartered in the Delhi NCR region. Its own account of its history is that the founder director began the warehousing vertical to add value for existing clients, that the first client came on board in 2008 and that operations started from a single warehouse. Today it claims more than 1 million square feet of warehouse infrastructure, more than 200 businesses served, more than 100,000 active SKUs under management and 12 or more locations running on one warehouse system. It holds ISO 9001:2015 and ISO/IEC 27001:2022, and cites an Intertek score of 93% for its Sonipat facility.

The published network covers Delhi, Noida, Gurgaon, Ghaziabad, Kundli, Sonipat, Rohtak, Bhiwandi, Bangalore, Hyderabad, Chennai, Kolkata, Ahmedabad, Guwahati and Indore. Service lines are B2B warehousing, B2C warehousing, ecommerce fulfilment, quick commerce fulfilment, same day delivery, transportation, value added services such as kitting and labelling, and returns management. The industries it names are ecommerce, apparel, FMCG, electronics, automotive, pharmaceuticals, beauty, home and furniture, manufacturing, publishing and sports.

This is a 3PL, not a marketplace and not a sales channel. In the unified model an AAJ warehouse is a locations row of type fulfilment_centre, it is the authoritative source of inventory for the SKUs held there, it sets fulfilment_type to 3pl on the orders it ships, it produces shipments through AAJ Swift or a partner carrier, and it produces returns receipts with a grading decision. It never produces listings or settlements, though it does raise storage and handling invoices that belong in settlements.fees[] once someone types them in.

The three systems AAJ names

API access

There is no developer console and no application to register. Credentials, if any exist, come out of an onboarding conversation after a warehousing contract is signed. What AAJ states publicly about connectivity, on www.aajscm.com/technology, is that it has 60 or more marketplace and platform integrations, ERP connectivity to SAP, Tally "and more", Unicommerce, "Custom ERP via API", and an "Open API" to "connect any platform not listed above" with "no additional development overhead on your side". It also says integration setup costs are covered by AAJ up to a defined threshold and that most integrations are completed within the first week of onboarding.

Read that carefully before planning work. The promise is that AAJ's own team builds the connector to your system, which is the opposite of a documented API you build against. For a unified database that is a problem, because it means the interface shape is negotiated per client rather than versioned, and there is no changelog or deprecation policy to track. No API version numbers, no SDKs in any language and no Postman collection were found. A GitHub search returned no client library, specification or integration code for AAJ or AAJ SCM.

Authentication

Not published. What was observed on 2026-09-22:

  1. app.aajscm.com returns HTTP 301 to https://wms.aajscm.com/.
  2. wms.aajscm.com serves an ASP.NET style web application whose title is "WMSOnWeb", with a form login and session behaviour. No token endpoint, no OAuth redirect and no API key field is exposed to an unauthenticated visitor.
  3. docs.aajscm.com serves an internal document review portal that signs in with Microsoft. It is unrelated to client integration.
  4. api.aajswift.com resolves and answers {"statusCode":404,"message":"Resource not found"} as JSON for unknown paths, which is a framework level handler rather than a documented API root. /docs, /swagger, /api-docs, /api/docs, /openapi.json and /swagger.json all return 404, so no specification is published there.

No token lifetime, scope model or multi account arrangement can be stated. For a brand with stock in more than one AAJ facility, the portal is described as a single login with a unified inventory view across all locations, so the natural expectation is one credential per client covering every warehouse, with location_id as a field rather than as a separate account. That is inference from the product description, not documentation.

Objects we can read

Nothing has a published endpoint, so no sample responses can be given. What exists as data, and where it lives, is worth recording because it is what you will ask for in the contract.

Orders

Order state from intake to dispatch is visible in the client portal and the Power BI dashboard, including order accuracy and turnaround time against platform SLA. AAJ says dispatch timelines are configured per platform and that COD remittance is mapped to each marketplace settlement cycle with order level discrepancy flags. Endpoint: not published.

Order items

Implied by SKU level picking and scan verification at pack out. No separate surface is described. Endpoint: not published.

Products and listings

AAJ holds a SKU master with batch, expiry and storage rules per product type, created during onboarding. It is not a sales channel, so there are no listings, prices or channel identifiers. Endpoint: not published.

Inventory

This is the most valuable object and the clearest gap. AAJ describes live stock levels by SKU, bin location, batch and expiry, updated on every scan across all facilities at once, with continuous cycle counting and an automatic comparison of system count against physical count. The claimed inventory accuracy is 99.75%. All of it is portal and dashboard only. Endpoint: not published.

Shipments and tracking

Warehouse dispatch triggers a transport booking in AAJ Swift TMS automatically, with live status from pickup to delivery and digital proof of delivery retained for 90 days. Tracking for the transport leg belongs to /connectors/aaj-swift. Endpoint for the fulfilment side: not published.

Returns and cancellations

Returns are received, scanned, inspected and graded into restock, rejection, repair, return to brand or disposal, with SKU level inventory updated once verified, photo and video evidence attached for marketplace disputes, and a return discrepancy report shared with the brand. AAJ claims a 98% restock recovery rate and return processing within 24 to 48 hours. Endpoint: not published.

Payments and settlements

AAJ raises storage, handling, packaging and freight charges to the brand. No invoice or fee API is described. COD reconciliation per marketplace is reported in the dashboard, not exposed as data. Endpoint: not published.

Customers

Ship to details pass through the warehouse on the label. AAJ does not present itself as a source of customer records, and any consignee data it holds is PII belonging to the brand's channel. Endpoint: not published.

Locations

The 15 city warehouse pages on the public site are the only machine readable list of the network, and they are marketing pages, not an API. Endpoint: not published.

Writing back: listings, price and stock

AAJ is not a sales channel, so there is no listing, price or stock write in the marketplace sense. The two writes a fulfilment connector needs are an inbound advice, telling the warehouse that a consignment is arriving with its expected contents, and an outbound order release, telling the warehouse to pick and ship. Neither has a published endpoint. In practice both go through the client portal or through whichever channel or ERP connector AAJ's team wired up during onboarding, which means the brand's Shopify, Amazon, Flipkart, Meesho, Myntra or Unicommerce account is the write path and AAJ pulls from it. If your system of record is none of those, the "Open API" claim is the thing to get specified in writing, with a schema, before signing.

Webhooks and notifications

Not published. Nothing describes event types, a subscription call, a signing secret or a retry policy. Since the Power BI dashboard is described as live, some push or near real time feed exists internally, but it is not offered to client systems.

With no push, the fallback is to poll the channel rather than AAJ: read stock and order status from the marketplace or storefront that AAJ is already synced with, and treat AAJ as the physical explanation for movements you observe there. If a direct feed is negotiated, a 15 minute pull for inventory by SKU and location and a 5 minute pull for order status is the cadence that matches marketplace stock update expectations without asking for streaming.

Rate limits and pagination

Not published. No quota numbers, no headers, no pagination model. Any limit will be whatever the per client interface is configured to allow, so it belongs in the same written specification as the endpoints.

Mapping to the unified model

Gaps and open questions

  • The "Open API" is the whole question. It is claimed on the technology page in one line and nowhere substantiated. Ask for the schema, the authentication method, the sandbox and the change policy in writing before treating AAJ as a data source.
  • The WMS provenance is contradictory. The marketing pages describe AAJ Pro WMS as in house with no licence fee passed to the client, while the client login is titled "WMSOnWeb". If it is a licensed product, the integration capability is the vendor's, not AAJ's, and no vendor site resolves under that name to check. This is worth one question on the onboarding call.
  • No inbound advice mechanism is described anywhere. For a brand sending stock to the warehouse, that is the first thing to pin down: file, portal form or endpoint.
  • Returns grading is unusually well described for an Indian 3PL, including video evidence retention, but there is no stated way to pull a grading decision programmatically, which is exactly what a marketplace dispute workflow would need.
  • Whether "AAJ Enterprise" is still used as a contracting entity name, or only as a legacy domain redirect, was not established.

Sources

  • www.aajscm.com/technology, read 2026-09-22: the connectivity and API claims, the integration list, cost absorption and go live timing.
  • www.aajscm.com/technology/wms, read 2026-09-22: AAJ Pro WMS feature list, accuracy and SKU figures, returns handling, Power BI dashboard, TMS coupling.
  • www.aajscm.com/technology/tms, read 2026-09-22: courier allocation, tracking, POD retention, pin code coverage.
  • www.aajscm.com/services/ecommerce-fulfillment, read 2026-09-22: channel coverage, one inventory pool, COD reconciliation, SLA mapped dispatch.
  • www.aajscm.com/services/returns-management, read 2026-09-22: inspection and grading steps, restock rate, evidence and discrepancy reporting.
  • www.aajscm.com/about-us, read 2026-09-22: history, scale, certifications.
  • www.aajscm.com/sitemap.xml, read 2026-09-22: the complete public page list, which contains no developer or API page.
  • Host checks on api.aajscm.com, developer.aajscm.com, portal.aajscm.com, client.aajscm.com, login.aajscm.com, app.aajscm.com, wms.aajscm.com, docs.aajscm.com and api.aajswift.com, with a nonsense subdomain as a control, 2026-09-22.
  • Redirect chain aajenterprise.in to aajenterprises.com to www.aajscm.com, verified 2026-09-22.
  • easyecom.io/integrations, read 2026-09-22: where the name "AAJ Enterprise" appears, as unlinked text in the fulfilment group.