B2C API Surface Map

Two God Nodes, two distinct domains: Products (what you buy) and Party (where you buy it from).

1. What Does AutoCoreB2CProductServices Expose?​

42 methods across 5 functional domains:

A. Catalog & Part Lookup​

B. SAYT / Typeahead Search​

C. Inventory & Availability​

D. Saleability / Lifecycle Management (Admin APIs)​

E. Order Fulfillment Config​

F. Selling Location & Price Region Management​

2. What Does "Party" Mean in B2C Context?​

Not the end consumer. In AutoCore's B2C context, "Party" = a physical store location or warehouse in the alliance supply chain.

The AutoCoreB2CPartyServices hierarchy resolves like this:

ProductStore (storeId)
  └── payToPartyId → MEMBER (e.g., "Bumper-to-Bumper" franchise)
        └── DOMAIN_PARTY (franchise territory parent)
              ├── PART_STORE (individual retail location with physical inventory)
              └── DISTRIBUTOR (warehouse / distribution center)

LiferayId = the external CMS identifier for a store party. The B2C storefront sends liferayId instead of internal partyId — AutoCoreB2CPartyServices translates this on every request.

What AutoCoreB2CPartyServices exposes:​

3. Sequence Diagrams​

Flow A: Product Detail Page (getProductDetails)​

Flow B: Inventory Check (checkProductAvailability)​

Flow C: Store Locator (getMemberStoreOrDistributionCenter)​

Flow D: SAYT Typeahead (getSAYTByKeyword)​

4. Key Insight: Two Planes of Truth​

The B2C layer never does a full-join across all five planes simultaneously. Each API call touches only one or two planes — the storefront UI assembles the complete picture on the client side by making multiple parallel API calls.