Olabi

Olabi is a cloud point of sale and unified commerce platform from Mindscape Computing Private Limited, based in Indiranagar, Bengaluru. It is aimed at fashion and lifestyle retailers running multiple stores, and it bundles the store till with an omnichannel order management layer, store fulfilment, inventory, loyalty and analytics. The vendor cites more than 25 years of retail enterprise experience and names Myntra, Tommy Hilfiger, Mango, ASICS, Calvin Klein and Under Armour among its customers.

For a brand running Olabi, it holds store sales, stock across locations, the customer and loyalty record, and the routing and fulfilment state of omnichannel orders. The vendor says an API exists, describes it as "Olabi API's kit" and claims the platform is "Rest API capable", but publishes no endpoint, no authentication model, no sample and no developer documentation of any kind. That is the finding.

At a glance

What it is

Olabi is genuinely cloud, not a hosted desktop product, which puts it in a different integration category from Logic ERP, Ginesys POS or eShopaid. The vendor describes a "native true cloud platform" on AWS delivered as software as a service, and holds ISO 27001, ISO 27017, SOC 2 and GDPR certifications, with a Trust Vault compliance portal at compliance.olabi.ooo.

The published solution suite has six parts, and they are worth knowing by name because they are what a scoping call will be about:

• Consumer. Customer history, segmentation, loyalty with multiple tiers, social media integration, SMS and email marketing.
• OmniChannel. Webstore and marketplace integration, product catalogue and price management, order fulfilment, logistics, marketplace aggregator integration, endless aisle, a store associate app, one-click POS integration and a cross-channel order management system with rules-based item-level order routing against location inventory.
• Store Fulfillment. Buy online pick up in store, ship from store, order preparation, non-delivery and return to origin, store receipt of returned items, automated refunds, forward and return AWB generation, shipment status tracking, cash on delivery collections and cross-channel financial reconciliation.
• Phygital Store. The point of sale itself, with mobile and contactless payments.
• Inventory. Real-time inventory view across locations, inventory reservation, and stock availability published to e-commerce.
• Omni Insights. Analytics and consumer insight.

Note what is in that list: AWB generation, shipment tracking, cash on delivery collection and cross-channel financial reconciliation. Olabi is doing more of the logistics and settlement job than a typical till, which makes it a richer source than its category suggests, if the API turns out to expose it.

API access

No developer signup, no console, no published key issuance and no published plan.

What the vendor actually says, from its own pages read on 2026-09-22:

• On the services page: "Integrate through native and certified connectors with a wide range of applications" and "Olabi API's kit available".
• On the why-Olabi page: "Olabi's API integration platform provides for seemless, hassle free integration with Payment gateways, Logistic partners, CRM, ERP systems etc..ensuring that your existing software investments" are preserved. Spelling as published.
• On the home page: the platform is "Rest API capable", with pre-built integrations to marketplaces, third party logistics warehouses and payment processors.

Read together, that describes an outbound integration platform: Olabi connecting to other systems through connectors it owns. It does not say that a third party can call Olabi. The distinction matters for scoping, and it is the first thing to establish with the vendor: is the API kit something Olabi calls out with, something a customer can call in with, or both.

What was checked and found absent, on 2026-09-22:

• api.olabi.ooo, docs.olabi.ooo and app.olabi.ooo all resolve to one shared hosting address and none completes a TLS handshake or serves content. They look like wildcard artefacts rather than real services.
• Certificate transparency for olabi.ooo lists only the apex, a wildcard, www, compliance and pre-release. No certificate has ever been issued to an API or documentation host.
• Postman public search returns no Olabi or Mindscape Computing collection and no request against any Olabi host.
• GitHub has no Olabi or Mindscape Computing organisation, repository or SDK.
• No API, developer or integration documentation page exists anywhere on the product site. The site's entire navigation is solution, services, customers and company.

No SDK, no OpenAPI specification and no Postman collection exists in any form.

Authentication

Not published. No token endpoint, header name, key format, scope model or lifetime has been made public by Olabi or by any third party. Nothing can be stated here without inventing it.

What can be said safely for planning: Olabi is multi-tenant software as a service on AWS, so expect a shared API host and a per-tenant credential rather than the per-installation credential and base URL that the on-premise Indian retail products force on you. That is a materially better starting position. Expect the credential to be issued by Olabi rather than self-served, given the enterprise sales model and the compliance posture.

Multi-account handling, for a group with several retail entities, is unknown.

Objects we can read

No endpoint is published for any object. The list below is the object inventory taken from Olabi's own solution pages, so a scoping call can ask for the right things by the vendor's own names.

Orders

Cross-channel orders from the webstore, marketplaces and the store, with rules-based item-level routing against location inventory. Store bills from the point of sale are a separate flow.

Order items

Item-level routing is called out explicitly, so lines are routed independently of the order, which means a single order can fulfil from several locations. Any mapping must allow for that.

Products and listings

Product catalogue management and price management, published out to a webstore and to marketplaces. This is the closest Olabi comes to a listing object.

Inventory

Real-time inventory across locations, with reservations as a distinct concept and a published availability feed to e-commerce. Reservations matter: available and reserved are separate quantities in this model, which maps cleanly onto our quantity_available and quantity_reserved.

Shipments and tracking

Forward and return AWB generation, shipment status tracking and return to origin handling, through pre-built integrations with logistics providers. Olabi holds the carrier and tracking state rather than only the dispatch.

Returns and cancellations

Return to origin, store receipt of returned items and automated refunds.

Payments and settlements

Mobile wallets and payment gateways are pre-integrated, cash on delivery collections are tracked, and there is a named cross-channel financial reconciliation capability. Whether any of that is readable is unknown.

Customers

Customer history across store visits and purchases, segmentation, and a multi-tier loyalty programme. All PII.

Locations

Stores are first class, and store fulfilment is a core capability, so a location object certainly exists internally.

No field name, sample response or endpoint can be quoted, because Olabi has never published one.

Writing back: listings, price and stock

For Olabi, read this as pushing sales orders, invoices and stock adjustments in.

Nothing is documented. What is known indirectly:

• Olabi already accepts orders from external channels, since webstore and marketplace orders flow into its cross-channel order management. An inbound order path therefore exists, at minimum through the vendor's own connectors.
• Olabi already pushes catalogue, price and stock outwards to a webstore and to marketplaces. An outbound path exists.
• Whether either path is exposed to a third party, and by what mechanism, is unpublished.

If a brand needs orders pushed in, the shortest route may be to find out which marketplace aggregator connectors Olabi already has and whether the brand's channel is one of them, rather than commissioning a custom integration.

Do not assume a stock write is available. On a platform that owns inventory reservation and cross-channel availability, a direct stock override is often deliberately closed.

Webhooks and notifications

Not published. No event catalogue, no subscription mechanism, no signature scheme and no retry policy.

Until the vendor says otherwise, assume polling, and assume the cadence will be negotiated rather than documented. As a true multi-tenant cloud on AWS, Olabi is a safer polling target than the on-premise products in this catalogue, but that is an argument about risk, not a licence.

Rate limits and pagination

Not published. No quota number, no header, no page size and no cursor model has been made public. There is not even a commercial proxy for a limit, as there is on AlignBooks, since Olabi publishes no pricing.

Mapping to the unified model

No Olabi field name has ever been published, so this table maps unified fields to Olabi capabilities, not to real field names. Every right-hand cell is a concept to confirm with the vendor.

Gaps and open questions

• Everything technical is unverified. The existence of the API rests on three first party marketing sentences and nothing else.
• The direction of the API is the first question. "API integration platform" in the vendor's wording reads as Olabi calling out to payment gateways, logistics partners, CRM and ERP. Whether a third party can call in is not stated anywhere.
• Whether the API is REST with JSON is an inference from "Rest API capable", not a fact.
• No authentication model, no rate limit, no pagination model, no error format and no versioning policy is published.
• No sandbox is offered publicly. pre-release.olabi.ooo responds but is almost certainly an internal environment.
• Whether the settlement and reconciliation data is exposed is unknown, and it is the most differentiated data Olabi holds.
• Whether item-level routing means a line can have a different status from its order is unconfirmed, and it changes the order_items mapping.
• Pricing, contract terms and minimum size are not published anywhere.
• Mindscape Computing Private Limited is the legal entity. Any due diligence should be run against that name, not against "Olabi".
• Good news for a future conversation: the compliance posture is strong for a vendor this size, with ISO 27001, ISO 27017, SOC 2 and GDPR certifications and a public trust portal. A vendor that has been through SOC 2 usually has an answerable security questionnaire and a documented API, even if it is not on the public web.

Sources

• Olabi home page, read 2026-09-22. Mindscape Computing Private Limited, Bengaluru address, the "Rest API capable" statement, AWS true cloud and software as a service positioning, named customers
• Olabi services page, read 2026-09-22. Source of "Olabi API's kit available" and the pre-integrated ERP, loyalty, CRM, business intelligence, payment, wallet and logistics statements
• Olabi why-Olabi page, read 2026-09-22. Source of the "API integration platform" sentence
• Olabi solution suite page, read 2026-09-22. Source of the module and capability inventory including AWB generation, shipment tracking, cash on delivery collections and cross-channel financial reconciliation
• Olabi certifications page, read 2026-09-22. ISO 27001, ISO 27017, SOC 2 and GDPR
• DNS and certificate transparency checks on 2026-09-22: api.olabi.ooo, docs.olabi.ooo and app.olabi.ooo resolve to a shared hosting address and serve nothing; certificate records list only the apex, a wildcard, www, compliance and pre-release
• Postman public search for olabi and mindscape computing, run 2026-09-22: no collection and no request against any Olabi host
• GitHub repository and code search for olabi and olabi.ooo, run 2026-09-22: no vendor owned repository or SDK. All matches are unrelated projects sharing the name