Engineering Docs¶
Internal documentation for the PopSockets engineering team — how our systems fit together, how orders flow, and how we build.
Start here¶
-
Systems Architecture
The 30,000-foot view — what talks to what, what data flows where, and why. The whole landscape on one page.
-
Camel Integration Layer
The
cm-*microservices that wire storefronts, OMS, warehouses, and retailer EDI together — the middleware everything flows through.
Order flows¶
-
OMS
The Rails app that owns the post-checkout order lifecycle — storefront through NAV release, batching, fulfillment, and payment capture.
-
B2C Order Flow
A direct-to-consumer order end to end: SFCC → NAV → (print) → Cirro → shipped and captured.
-
EDI B2B Pipeline
The B2B retail order lifecycle — the retailer's purchase order (850) through fulfillment, shipping, and invoicing (810).
-
PrintStation & BatchStation
The custom / personalized print pipeline — how OMS hands printable orders to BatchStation and PrintStation.
B2B retail¶
-
Cirro B2B by Vendor
Per-retailer specs — the real 850, the real 940, and exactly what we send Cirro, one page per vendor.
-
Carton Sizing
For a given product, how many units are in a full middle carton — the number that drives B2B carton sizing and PopForge test quantities.
More¶
-
Design Docs
Forward-looking designs the team has agreed on but hasn't necessarily built yet.
-
AI Strategy
Integrating AI into your dev workflow — getting started, bootcamp, agreements, and hands-on exercises.