Unified retail platform

Run AIERP as one connected system across POS, catalog, inventory, sync, fulfillment, and store operations.

AIERP brings store-facing checkout, canonical catalog and inventory, dark-store fulfillment, integrations, deployment tooling, and operational guidance into one platform surface.

Explore the platform See the architecture

Retail stack POS, store hub, catalog, sync

Deployment model SaaS or customer-hosted

Docs audience Product, ops, integrators, platform teams

Operational truth Catalog metadata, stock by location, store status, sync health

Primary flows Sell, sync, replenish, fulfill, deploy, observe

Start In The Right Place

First read

Platform overview

Get the system model, product boundaries, and the fastest path to understanding what AIERP covers.

For product and design

Products

See how POS UI, Store Hub, and the platform services fit together as one retail operating surface.

For platform engineering

Architecture

Understand ownership across catalog, inventory, dark stores, sync, APIs, and event-driven flows.

For integration teams

POS and ERP integrations

Plan source-system ingestion, contract shape, and operational expectations for external partners.

Platform At A Glance

What AIERP documents well

Documentation that explains the product, not just the repository.

This docs site is meant to help someone understand how AIERP behaves in production: who owns what, how data flows, how environments are deployed, and how teams operate under pressure.

Product surfaces

POS UI, Store Hub, developer surfaces, and the services behind daily retail operations.

Operational flows

Inventory updates, dark-store orderability, POS sync, deployment models, and support runbooks.

Implementation detail

API conventions, event contracts, repo ownership, platform blueprints, and extensibility guidance.

Documentation Paths

Deployment

Use Cloudflare-hosted docs, customer Kubernetes, or internal-only delivery depending on the environment.

Operations

Runbooks, ownership maps, and production expectations for support and platform operations.

Developer

Read API patterns, event contracts, and guidance for building polished documentation and product surfaces.

Deployment Modes

Public docs

`docs.aierp.aabhat.com`

Use the hosted docs site for product marketing, architecture communication, and partner onboarding.

Private deployment

Customer-hosted docs

Publish the same MkDocs build behind a customer network or expose it under an internal `/docs` route.

Application boundary

`pos-v2.aabhat.com` stays separate

Keep the live application focused on operations while the docs experience stays product-led and navigable.

Documentation Principles

The docs should explain the product, not just the codebase.

Architecture pages should make ownership and data flow unmistakable.

Runbooks should support operators under time pressure.

Animations and visuals should clarify the system, not decorate empty space.