Foundation

This page provides a combined overview and core feature summary of the Foundation Service for the Infosys Equinox platform.

Overview

What is Foundation Service?

Foundation Service is the platform setup and configuration backbone of Infosys Equinox commerce. It acts as the master registry that every other microservice depends on. Before products are created, orders are placed, or users are registered, the business and store structure that owns that data must already exist in this service.

When a new merchant (tenant) signs up to use the Equinox platform, the first administrative step is creating a Business and at least one Store through this service. Other services then scope their data to those identifiers.

If Foundation is not set up first:

• PIM Service cannot create product catalogs (no store to attach them to).
• OMS Service cannot accept orders (no store context to validate against).
• User Service cannot create user accounts (no instance scope to assign them under).
• Inventory Service cannot track stock (no locations to store inventory at).

How the Platform Uses This Service

Every request in the Equinox platform carries three key identifiers in the JWT or request headers:

All collections in this service, and in every other Equinox service, filter by these identifiers to keep tenant data isolated.

Platform Architecture – Where Foundation Fits

                    ┌─────────────────────────────────┐
                    │       Foundation Service        │
                    │ (businesses, stores, locations, │
                    │  sites, sellers, master data,   │
                    │  feature flags, batch pipelines)│
                    └──────────────┬──────────────────┘
                                   │ provides context for
          ┌──────────┬─────────────┼──────────┬──────────┐
          ▼          ▼             ▼          ▼          ▼
         PIM        OMS       Inventory     User      Loyalty
      (products)  (orders)      (stock)    (users)    (points)
          │          │             │
          └──────────┴─────────────┘
                     │
      Marketplace / Cart / Subscription

Foundation is the only service that does not depend on another Equinox domain service. All other domain services depend on it.

First-Time Tenant Setup Order

1. Create a Business (POST /v1/businesses) — top-level organization record.
2. Create root Store (POST /v1/stores) — global/HQ store at hierarchy level 0.
3. Create child Stores if needed — regional, district, or leaf stores parented to level 0.
4. Create Locations (POST /v1/locations) — physical warehouses, stores, or dark-stores attached to stores.
5. Create Sites (POST /v1/sites) — online storefronts linked to a store.
6. Create Sellers (POST /v1/sellers) — vendor profiles for multi-vendor models.
7. Configure Service Properties — cross-service config consumed by PIM, OMS, and others.
8. Configure Feature Flags — enable/disable features per instance.
9. Set up Batch schedules — scheduled imports/exports through ETL pipelines.

Related Services

Core Features

Domain Areas

Key Capabilities

• Store hierarchy with automatic inheritance and child-level overrides.
• Redis-cached effective configuration for fast hierarchy resolution.
• Up to 4 hierarchy levels (0-3): Global/HQ – Regional – District – Leaf.
• Circular reference prevention in hierarchy updates.
• FEFO-aware location management with ship-from-store eligibility.
• EventBridge-driven batch scheduling with real-time callback status updates.
• In-memory development mode using in-memory stubs (FOUNDATION_USE_INMEMORY=true).
• Strict multi-tenant isolation via instanceId-scoped repository queries.
• Pluggable per-instance extension handlers for validation and lifecycle hooks.
• Consistent pagination defaults (page=1, limit=10, maxLimit=100) and status model (ACTIVE=1, INACTIVE=0).

Technology Stack

Revision History

2026-08-04 | AN – Page created and uploaded the contents