A proposal for the BC platform
Sony wanted employee-only promotions.
BC couldn't do it.
A representative scenario: a Sony merchandise manager creates an employee discount, the code gets shared
on a deal-sharing site, and Finance flags a margin spike. The store has no way to restrict the promotion
to @sony.com email addresses — or any other customer attribute. This proposal adds that capability.
Shopify has had native email-domain targeting as of 2023–2024.
BC's current engine exposes only customer.ID and customer.GroupID at promotion evaluation time.
Executive
Is this worth the bet?
Market position, competitive gap, and the 3-phase delivery model with phased scope decisions.
Evaluator
What would merchants see?
BigDesign-faithful conditions editor mockup — the Sony employee-discount setup in the Advanced Promotion Manager.
Engineering
What would we actually build?
CEL evaluation architecture, the structural gap in the Go service, two-repo delta, and why now is the right moment.
Try
BigDesign-faithful mockup of the proposed "Customer" condition panel in the Advanced Promotion Manager.
Discover
Market position, the Sony incident, phased delivery rationale — the bet we are placing and why it wins.
Build
CEL architecture, PromotionEvaluationContext struct, two-repo delta, phased delivery model. Engineering audience.
Operate
Merchant setup guide — how to configure an employee-only promotion using the proposed UI. Step-by-step.
Roadmap
Phase 1 / 2 / 3 delivery timeline. What is planned, what is deferred, what the dependencies are.
Inspect
Research corpus (5 files), architectural decision lineage, why CEL over OPA, why no metafields.