Executive Decision
Recommended Program
Full Replatform
Scope
Commerce + Email + Data
Realistic Timeline
10-12 Months
Decision Driver
Growth Velocity
This is not a quick cosmetic migration. It is a system replacement program for merchandising, checkout agility, lifecycle data quality, and experimentation speed.
Why Move Now
Quantified Platform Reality
Commerce Stack Constraints
- NetSuite is ERP-first and introduces API/concurrency constraints for high-frequency storefront orchestration.
- Custom cart means 100% internal ownership of checkout velocity, security, and optimization backlog.
- Large catalog footprint (28,250 products) amplifies cost of every slow release cycle.
Lifecycle Stack Constraints
- Bronto was sunset permanently in 2022; its model is not a future option.
- Listrak supports enterprise retail but has more restrictive data patterns and smaller native integration surface than modern growth stacks.
- Delayed migration keeps segmentation and experimentation cycles slower than market leaders.
Business implication: the longer the current architecture remains unchanged, the wider the execution-speed gap becomes between BBQGuys and faster-moving commerce competitors.
Current vs Target
Page Architecture: What Exists vs What Is Needed
| Layer | Current State | Target State |
|---|---|---|
| PDP Content Model | Rich sections exist (specs, dimensions, reviews, warranty, shipping) but delivery speed is stack-constrained. | Componentized PDP schema with controllable blocks and faster release cadence for merchandising and trust experiments. |
| PLP Trust Signals | Trust cues appear weaker at browse stage than PDP stage. | Explicit trust-first PLP cards (rating/review confidence, shipping clarity, offer tags) before click-through. |
| Offer & Promo Logic | Promo orchestration depends on legacy integrations and custom behavior. | Centralized, testable promotion engine with deterministic rules and auditability. |
| Checkout Ownership | Custom cart requires full internal ownership for every optimization. | Modern checkout stack with accelerated payment flows and lower maintenance overhead. |
| Lifecycle Data | ESP model limits segmentation agility and unified event strategy. | Unified profile + event model with faster campaign iteration and clearer attribution loops. |
Delivery Plan
10-12 Month Phased Program
Phase 0 (Month 1): Discovery + Architecture Lock
Confirm source systems, canonical entity model, integration map, and final target-stack decisions.
Confirm source systems, canonical entity model, integration map, and final target-stack decisions.
Phase 1 (Months 2-3): Data Foundations
Build mapping specs, transformation rules, ID strategy, and reconciliation framework for products, variants, customers, orders, inventory, promotions, and consent.
Build mapping specs, transformation rules, ID strategy, and reconciliation framework for products, variants, customers, orders, inventory, promotions, and consent.
Phase 2 (Months 4-6): Commerce Build
Implement target catalog/PDP/PLP/checkout architecture; reproduce core parity while improving trust surfaces and performance foundations.
Implement target catalog/PDP/PLP/checkout architecture; reproduce core parity while improving trust surfaces and performance foundations.
Phase 3 (Months 6-8): Lifecycle Migration + Event Model
Migrate profiles and consent states, stand up event ingestion, rebuild priority flows, and validate deliverability/compliance.
Migrate profiles and consent states, stand up event ingestion, rebuild priority flows, and validate deliverability/compliance.
Phase 4 (Months 8-10): UAT, Shadow Runs, Cutover Rehearsal
Run parallel validation, delta migrations, financial/identity reconciliation, and full go/no-go rehearsal.
Run parallel validation, delta migrations, financial/identity reconciliation, and full go/no-go rehearsal.
Phase 5 (Months 10-12): Cutover + Stabilization
Controlled launch, rollback safeguards, hypercare, and optimization sprint cycles.
Controlled launch, rollback safeguards, hypercare, and optimization sprint cycles.
Specification Requirements
Must-Have Technical Specs
- Canonical identifiers for every entity and stable source-to-target mapping tables.
- Deterministic transformation rules for money, tax, enums, timestamps, and unit normalization.
- Explicit product spec taxonomy (materials, dimensions, BTU, fuel, configuration) for reusable PDP rendering.
- Reconciliation templates: counts, uniqueness, referential integrity, and financial accuracy.
- Consent invariants: no inferred marketing consent without explicit legal basis mapping.
Risk Controls
Cutover Gates and Rollback Triggers
- Identity or line-item mapping failure rate exceeds defined tolerance.
- Aggregate or sampled financial reconciliation mismatch exceeds tolerance.
- Consent validation failure in any send-eligible profile segment.
- Checkout/UAT failure beyond threshold in mission-critical journeys.
- Immediate response: disable sends, revert routing/flags, preserve migration logs for RCA.
Commercial Rationale
Why NetSuite-Era Commerce + Legacy Lifecycle Limits Growth
This recommendation is not anti-enterprise. It is pro-growth velocity. In high-SKU ecommerce, slow test cycles and fragmented decisioning become compounding disadvantages.
Release Cycle Drag: ERP-centered commerce orchestration and custom-cart ownership typically increase effort per experiment and per checkout change.
Lifecycle Agility Gap: constrained profile/event models reduce speed of segmentation, personalization, and campaign iteration.
Competitive Risk: faster competitors compound gains through more frequent testing while slower stacks compound backlog.
Bronto Context: Bronto is sunset (2022), confirming that legacy ESP patterns are no longer a viable long-term growth path.
Recommendation
Approve Phase 0 discovery immediately and treat this as a 10-12 month modernization program with strict gates. The objective is not just migration parity; it is restoring growth velocity in commerce and lifecycle execution.