Cloud Commerce
ServerBy Intelligence FactoryLet’s talk ↗

In practice · B2C companion

The same commerce core can support a shorter consumer path.

Northline’s consumer filter-kit order demonstrates a configuration context, not a claim that every installation ships with one universal storefront.

Companion story

A consumer basket reaches payment and fulfillment with the same separation of concerns.

One fictional reference company

Northline Workshop

Northline is a synthetic industrial business used consistently across every story. It buys a configured precision actuator through a negotiated account path and offers the same product through a separately configured consumer channel. Numeric IDs below match the integer types used by the application. Human-facing references are labeled separately. No record, result or screenshot on these pages comes from a customer environment.

Lead
Northline Workshop · Avery Chen · LeadID 1042
Account
Northline Workshop Account · AccountID 220
Product
NL-ACT-240 Precision Actuator · ProductID 240 · product code NL-ACT-240
Quote / order
BasketID 7841
Consumer basket
BasketID 9108
Conversation
Avery Chen · call reference NL-C-031 · note reference NL-N-118
Change request
Northline minimum-order rule · release identity pending Phase 2

A fictional consumer selects the enabled offer identified by product code NL-ACT-240 and ProductID 240, reviews quantity, shipping and total, and checks out BasketID 9108. The storefront experience, tax, payment and fulfillment integrations are installation-specific even though the basket/payment semantics come from the shared foundation.

  1. Create the basket

    The selected channel creates BasketID 9108 and line items for ProductID 240.

  2. Review the order

    The buyer confirms quantity, delivery information, tax, shipping and total before payment.

  3. Submit payment once

    The configured processor returns a result that must be reconciled before retrying a delayed response.

  4. Complete fulfillment

    Fulfillment runs separately. A paid-but-unfulfilled basket remains paid while the fulfillment issue is resolved.

published proofNorthline consumer confirmation showing a single local-test payment for Basket 13.
Verified Northline consumer checkout through the configured product route.Local-test provider evidence: $256.80 paid once, unfulfilled, with cross-owner receipt access denied.Runtime evidence northline-launch-proof-2026-09-16 · northline-proof-checkpoint-2026-09-16

Implementation context

Shared semantics do not erase channel differences.

Guest vs. account checkout

This is an installation decision; do not infer a universal account requirement from the admin workflow.

Taxes and shipping

Providers, jurisdictions and rules are configured for the installation.

Payment succeeds, fulfillment fails

Reconcile the paid basket and retry fulfillment; do not charge again.

Configure products Verify payment and fulfillment Compare the B2B journey

Evidence boundary

The companion is source-backed but not yet captured.