Amerimatter Architecture

Stack shape for Amerimatter brand commerce: SnapNGo CLI scaffolds the spine; domain modules cover catalog, inventory, cart/orders, and checkout payment for goods.

Project

Amerimatter

Audience

Lead eng · architects

Stack

SnapNGo · Catalog · Orders · Commerce pay

Target topology

  snapngo init / add / up
        │
        ▼
┌──────────────────────────────────────────────────┐
│  Host shell · catalog / cart remotes (print UI)  │
└───────────────────────┬──────────────────────────┘
                        ▼
                 API Gateway
                        │
     ┌──────────┬───────┼────────┬────────────┬──────────┐
     ▼          ▼       ▼        ▼            ▼          ▼
   auth      media   catalog  inventory    orders   commerce pay
 (buyer/     (presign) (SKU)   (stock)     (cart)   (checkout)
  staff)                                           shopper → merchant
     │          │       │        │            │          │
     └──────────┴───────┴────────┴────────────┴──────────┘
                        │
              Postgres · object storage (S3)
              tenants/{storeId}/products/...

packages: @snapngo/shared · @snapngo/observability · brand UI tokens

SnapNGo spine

Scaffold with SnapNGo: gateway, auth defaults, observability packages, module ports and env. Domain modules attach for commerce. Host shell loads catalog and cart surfaces under the Amerimatter design system (paper / ink / vermilion).

Money model

• Checkout payments — buyer pays for metal / SKUs / cart lines (PaymentIntents or equivalent)
• Orders service — cart, line items, state machine, history
• Inventory — ATS, reserve on checkout start, commit or release on success/cancel
• Catalog — SKUs, categories, media refs, MSRP; stock stays out of product rows as the long-term rule

Commercial center is catalog → cart → pay → fulfill. Payment attaches to the order, not to a recurring platform seat plan.

Critical path: place order (draft)

1. Browse catalog (gateway → catalog)
2. Add to cart (orders) · optional stock check (inventory)
3. Checkout → commerce pay session
4. Inventory reserve → payment confirm → order commit
5. Release reserve on cancel / failure

Auth roles (draft)

• Staff / admin — catalog and order ops
• Buyer account — optional logged-in customer; guests may cart with session id

Media

Product images via presign under tenant prefix; CDN for public catalog reads. Hard borders and print assets follow the brand system, not generic SaaS illustration.