Crème Collective — 2026 Roadmap

2026

Crème Collective · DataStudios

Automation
& Growth
Roadmap

Three workstreams in parallel · Q2 – Q4 2026

01CRM Migration

02Warehouse Automation

03Monthly Report Rollout

Following three days of discovery sessions with Danny Castro, three engagement options were prepared for Leila and Jeremy's review. All options share the same goal — warehouse operations efficiency before Q4 — but differ in resourcing, pace, and what gets deprioritized. Option C was selected.

Plan A

Full-Time
Parallel Tracks

$20K / month · 5 months

Warehouse

Two near-FTE engineers + junior, dedicated to warehouse
Bucket 1 (Order Entry + EDI): all retailers done before August
Buckets 2–4 (Shipment, Routing, Billing): complete by November 1

Everything Else

Reporting Portal, CRM, Monthly Report rollout: all continue at current pace
No deprioritization across other workstreams

Not selected — budget increase required

Plan B

Hours Split
Across Everything

$10K / month · current rate

Warehouse

Warehouse competes with Portal, CRM, and Monthly Reports for the same hours
Bucket 1 (Order Entry + EDI): end of November / December — after busy season
No meaningful warehouse delivery before September

Everything Else

Portal, CRM, Monthly Reports: all move slowly and partially
Effectively status quo with warehouse added to an already full plate

Not recommended — nothing delivered before Q4

✓ Selected Plan

Plan C

Warehouse as
Primary Focus

$10K / month · current rate

Warehouse — Primary

Bucket 1 Spring Systems (Order Entry + EDI): target August 1
Bucket 1 Bamboo Rose + SPS: target August 1, may slip to end of August
Warehouse becomes the primary engineering priority

Continues in Parallel — Pace Subject to Warehouse *

Monthly Report rollout to all brands *
CRM migration — scoped to HubSpot baseline cutover *
Remaining portal sections deprioritized

Deferred

Buckets 2–4 (Shipment, Routing, Billing): end of 2026 / early 2027
Remaining CRM features + portal sections: end of 2026 / early 2027

* Both the Monthly Report rollout and the CRM migration are subordinate to warehouse — their pace flexes around Warehouse Bucket 1 progress, which is the priority.

This is what the current $10K/month retainer delivers across the three workstreams — Warehouse, CRM, and the Reporting Portal (of which the Monthly Report rollout is just one component). Warehouse is limited to Bucket 1 through August. The CRM baseline cutover proceeds (committed regardless of budget), but advanced CRM features, the remaining Reporting Portal sections, and Warehouse Buckets 2–4 all defer to 2027. The Monthly Report rollout continues but runs mid-July through end of October as it competes for shared hours.

(01)Current Plan Timeline — June through December 2026

Workstream

June

July

August

September

October

November

December

1 · Warehouse Automation

Bucket 1Order Entry + EDISpring Systems · Bamboo Rose · SPS

Bucket 1 — Order Entry + EDI · Jun – Aug

Buckets 2–4Shipment · Routing · BillingNot in current budget

Buckets 2–4 — Deferred → 2027

2 · CRM

CRM MigrationHubSpot Baseline CutoverCommitted · see CRM Project Timeline

CRM Migration — Baseline Cutover · Jun – Jul

CRM · RemainingAdvanced FeaturesPace subject to warehouse

Remaining CRM Features — Deferred → 2027

3 · Reporting Portal

Monthly ReportsBrand Report Rollout · 14 BrandsOne component of the portal

Monthly Report Rollout — Mid-July through End-October

Portal · RemainingOther Client-Facing SectionsDeprioritized under current budget

Remaining Portal Sections — Deferred → 2027

Committed Build

Stretched Rollout

Deferred → 2027

(02)What the Current Budget Means

Warehouse

Bucket 1 Only

Order Entry + EDI automation across Spring Systems, Bamboo Rose, and SPS Commerce — targeted through end of August. No Shipment/ASN, Routing, or Billing automation in this window.

The Q4 Risk

Billing Stays Manual

Bucket 4 (billing automation) is the Q4 bottleneck — and it defers to 2027. Without it, the October–December crunch repeats last year's capacity crisis. This is the gap the revised budget is designed to close.

Monthly Reports

Mid-July → End October

Rollout to the remaining 13 brands continues in parallel but competes for the same hours as warehouse work — realistically completing around end of October rather than mid-year.

Buckets 2–4

Deferred to 2027

Shipment + ASN automation, Transportation & Routing, and Billing — along with remaining CRM features and portal sections — slip to end of 2026 / early 2027 under the current budget.

Building on the current plan, these three options accelerate delivery with a temporary budget increase. Each tier adds distinct value — D lands the CRM, E adds fully-integrated reporting and faster order entry, and F completes the warehouse automation that protects Q4. We recommend Plan F — it is the only option that removes the holiday billing bottleneck before the Q4 ramp.

Plan D

CRM
Acceleration

$20K × 1 mo June

Delivers

CRM rollout + email tracking — baseline cutover mid-July
Detailed CRM Project Timeline (see deep dive)

Trade-off

Monthly reports slip — not ready in June
Warehouse stays at current scope

One-month bump — CRM only

Plan E

Plan D + Monthly
Reporting & Order
Entry Acceleration

$20K × 2 mo June – July

Everything in D, plus

All 14 monthly reports live by mid-August
CRM-integrated — reports read from the new CRM, not HubSpot
Order entry compressed — finished earlier than the August baseline

Trade-off

Warehouse Buckets 2–4 still deferred — Q4 billing stays manual

Two-month bump — CRM + reporting + faster order entry

Plan F

Plan E + Full
Warehouse Automation
Acceleration

$20K × 3 mo June – August

Everything in E, plus

Full warehouse automation — Buckets 2–4 (Shipment/ASN, Routing, Billing)
Billing automation — solves the Q4 bottleneck; system Q4-ready by Sep 30

Why we recommend it

Only plan that prevents last year's Q4 crunch from repeating
Hardening + Danny / Rita sign-off before October volume

Three-month bump — the complete foundation before Q4

(01)Combined Timeline — June through December 2026

Workstream

June

July

August

September

Oct · Q4

Nov · Q4

Dec · Q4

01 · CRMMigration + EmailCommitted · cutover mid-July

CRM Migration + Email — Cutover Mid-July

02 · Reporting PortalMonthly ReportsFollows CRM · through September

Monthly Reports — Follow CRM · Through September

03 · WarehouseBucket 1 (baseline)Order Entry through Aug

Bucket 1 — Order Entry (baseline)

Buckets 2–4 → 2027

Committed / Active

Rollout / Follow-on

Deferred → 2027

Q4 Holiday Ramp

(02)What Plan D Delivers

CRM

Accelerated + Email

CRM rollout with email tracking, baseline cutover mid-July. This is the one workstream Plan D firmly lands.

Reporting Portal

Reports Follow CRM

Monthly reports roll out after the mid-July cutover — completing July through September, rather than the end-of-July timing of the faster plans. Not CRM-integrated under Plan D.

Warehouse

Bucket 1 Only

Order entry stays at the current baseline through August. Buckets 2–4 defer to 2027.

Q4 Risk

Billing Stays Manual

No billing automation — the Q4 crunch repeats. Plan D buys CRM speed only.

(01)Combined Timeline — June through December 2026

Workstream

June

July

August

September

Oct · Q4

Nov · Q4

Dec · Q4

01 · CRMMigration + EmailCommitted · cutover mid-July

CRM Migration + Email — Cutover Mid-July

02 · Reporting PortalMonthly Reports · 14 BrandsCRM-integrated

All 14 Monthly Reports — CRM-Integrated · Mid-Aug

03 · WarehouseOrder Entry (compressed)Done earlier than Aug

Order Entry — Compressed, Done Earlier

Buckets 2–4 → 2027

Committed / Active

Deferred → 2027

Q4 Holiday Ramp

(02)What Plan E Delivers

CRM

Accelerated + Email

CRM rollout with email tracking, baseline cutover mid-July.

Reporting Portal

All 14 Reports · CRM-Integrated

Every brand's monthly report live by mid-August, reading from the new CRM — not HubSpot. One connected system.

Warehouse

Order Entry Compressed

Order entry finishes earlier than the August baseline. Buckets 2–4 still defer to 2027.

Q4 Risk

Billing Still Manual

No billing automation — the Q4 crunch remains. Plan E lands CRM + reporting + faster order entry, but not the holiday fix.

(01)Combined Timeline — June through December 2026

Workstream

June

July

August

September

Oct · Q4

Nov · Q4

Dec · Q4

01 · CRMMigration + EmailCutover mid-July

CRM Migration + Email — Cutover Mid-July

02 · Reporting PortalMonthly Reports · 14 BrandsCRM-integrated

All 14 Monthly Reports — CRM-Integrated · Mid-Aug

03 · WarehouseBuckets 1B – 4 · Full BuildAll four buckets

Buckets 1B–4 — Full Build · Jun–Aug

Hardening + Dry Run

★ Sep 30 · Q4 Ready

Active Build / UAT

Hardening

★ Q4 Ready

Q4 Holiday Ramp

(02)What Plan F Delivers — Everything, Before Q4

CRM + Reporting

Both Live by Mid-Aug

CRM cutover mid-July with email; all 14 monthly reports CRM-integrated by mid-August.

Warehouse

Full Build — Buckets 1B–4

All four buckets, including billing automation — the one workstream that removes the Q4 bottleneck. Built Jun–Aug.

September 30

★ Q4 Ready

Hardening + Danny / Rita sign-off complete. System stable and validated before the October holiday ramp — nothing trailing into Q4.

The original Plan A estimate was five months. Plan F delivers the same Q4-ready warehouse automation in three. Two things changed — one narrows scope, the other reduces risk. Neither cuts the automation that protects the holiday season.

Reason 1 · Narrower Scope

Monthly Report —
Not the Full Portal

Plan A bundled the entire Reporting Portal build — all client-facing sections — into the 5-month estimate
Plan F commits to the Monthly Report rollout exclusively
Remaining portal sections move to a later phase — removing that scope shortens the build

Less to build in the window

Reason 2 · Lower Risk

Bucket 1 Taught
Us the Systems

Delivering Bucket 1 gave us real insight into the systems, integrations, and effort — Camelot API, the EDI portals, the data shapes
That removes the estimation uncertainty that padded the original number
We can now commit to tighter, more confident timeframes for the remaining buckets

Estimate is de-risked, not guessed

Net effect: a more focused scope plus a de-risked estimate compresses the same Q4-ready outcome from five months to three — without cutting any of the warehouse automation that protects the holiday season.

The timelines hold only if the inputs below hold. Two items are genuinely on the critical path: the team's responsiveness — questions, approvals, access — and the product-dimension data for billing automation. Neither is something we can build around.

(01)What We Need From Crème

Cadence & Access · Critical Path

Twice-Weekly Stand-ups

Danny (Warehouse) and Tyler (Sales) have committed to stand-ups every Tuesday & Thursday. Responsive turnaround on questions, approvals, and access is mission-critical — delays here move the dates directly.

Data · By Mid-July

Product Dimensions

SKU dimensions + weights for all active brands loaded into Camelot. The highest-risk item — billing automation cannot compute charges for brands missing dims. A data task owned by Danny + brand contacts; no code workaround.

Access · By June 1

Credentials & Decisions

Camelot API auth, EDI portal logins, Nordstrom CTE portal, and the orders@ inbox + email forwarding. TecOMS retained — no middleware replacement in this window.

Inputs · As Needed

Walkthroughs & Brand Detail

Rita's full-cycle walkthroughs (Bamboo Rose / SPS / Bluemercury) when live orders are available; Tyler confirms per-brand retailer mix and wholesale-goal Sheet IDs.

(02)Assumptions & Scope Boundaries

✓

CRM Cutover On ScheduleMonthly reports are CRM-integrated, so their mid-August rollout depends on the mid-July CRM cutover landing on time.

✓

CRM Committed RegardlessThe CRM Project Timeline proceeds independent of which option (D / E / F) is chosen.

✓

Estimate BasisThe 3-month estimate assumes systems behave as observed during Bucket 1. Material new findings could shift timing.

✓

Human-in-the-Loop & Iterative TuningAI automation improves through feedback. The team's input during hardening — and through the live holiday season — is how the system is fine-tuned; human review is a designed part of the rollout, and performance compounds as the loop runs.

✓

Adaptive, Measured RolloutReal-world performance may lead us to phase deliberately — prioritizing the highest-value, most-ready components and giving others a more measured timeline. Scope is optimized toward the best Q4 outcome, with any trade-offs agreed jointly.

✕

Out of Scope · Reporting PortalThe full client-facing Reporting Portal build beyond the monthly report.

✕

Out of Scope · CRM FeaturesRemaining CRM features beyond the HubSpot-baseline cutover.

★

Shared Dependency TrackerA shared project group / tracker will give all stakeholders visibility into critical-path items across the full engagement.

Crème Collective · Automation & Growth Roadmap

Appendix

Detailed project timelines — the deep dives behind the consolidated plans

A1CRM Project Timeline

A2Warehouse Automation

A3Monthly Report Rollout

(01)Project Timeline

Phase

June 2026

July 2026

Wk 1

Jun 1–7

Wk 2

Jun 8–14

Wk 3

Jun 15–21

Wk 4

Jun 22–28

Wk 5

Jun 29–Jul 5

Wk 6

Jul 6–12

Wk 7

Jul 13–19

Wk 8

Jul 20–26

Wk 9

Jul 27–31

Phase 0Re-Import & Delta Sync SetupDataStudios

Phase 0 — Re-Import & Sync

Phase 1UAT Wave 1 — Sales ManagerTyler Kopp · tyler@cremecollective.com

Phase 1 — Tyler Kopp · Jun 9–20

Phase 2UAT Wave 2 — SalesLia Briehl · lia@cremecollective.com

Phase 2 — Lia Briehl · Jun 16–27

Phase 3UAT Wave 3 — Rest of Sales TeamRemaining sales reps · Jun 22 – Jul 5

Phase 3 — Rest of Sales Team · Jun 22–Jul 5

Phase 4Data Validation (Parallel)DataStudios · Concurrent with Phases 1–3

Phase 4 — HubSpot Parity Validation · Ongoing Jun 9–Jul 5

Phase 5Blue-Green Overlap WindowDataStudios + Crème · 5-day parallel run

Phase 5 — Blue-Green · Jul 6–12

Phase 6Cutover DayDataStudios + Crème · 4-hr rollback gate

★ Cutover — July 14, 2026

Phase 7Post-Cutover StabilizationDataStudios · 2-week support window

Phase 7 — Stabilization · Jul 14–31

Active UAT Phase

Parallel Validation

Blue-Green Window

Cutover Day

Stabilization

(02)Key Milestones

June 1, 2026

Project Kickoff

Full HubSpot re-import: contacts, companies, deals, activities. Delta sync (15–30 min pull) configured and tested.

June 6, 2026

Sync Confirmed

24h of delta events verified in sync log. Initial parity spot-check passes. UAT Wave 1 cleared to begin.

June 9, 2026

UAT Wave 1 Opens

Tyler Kopp begins 10-scenario validation. DataStudios attends first 1–2 sessions, then async feedback form.

June 16, 2026

UAT Wave 2 Opens

Lia Briehl begins sales-specific scenarios. Tyler Kopp handles peer onboarding. Waves overlap by 1 week.

June 27, 2026

UAT Complete

Both waves sign off. All P0/P1 issues resolved or triaged. P2 items deferred to post-cutover backlog.

July 5, 2026

Validation Sign-Off

Parity scorecard ≥ 95% across all objects. DataStudios + Crème stakeholder co-sign required to advance.

July 6, 2026

Blue-Green Opens

5-day parallel window. HubSpot = blue (active input). CRM = green (sync target). No CRM writes back to HubSpot.

July 14, 2026

★ Cutover Day

CRM becomes system of record. HubSpot restricted to read-only. 4-hour rollback gate active. Stabilization begins.

(03)Phase Dependencies

→

Phase 0 → Phase 1Re-import complete and 24h of sync events confirmed before Tyler Kopp begins UAT on June 9.

→

Phase 1 → Phase 2Tyler completes 80%+ of Wave 1 before Lia onboards. Overlap of 1 week (Jun 15–21) is intentional — Tyler peer-onboards Lia.

→

Phase 4 → Phase 5Parity scorecard ≥ 95% required before blue-green window opens. DataStudios + Crème stakeholder co-sign gates the transition.

→

Phase 5 → Phase 6Blue-green window must run 5 full days with no critical issues before cutover is authorized. Go/no-go decision on July 13.

→

HubSpot Access → All PhasesDelta sync requires read access to HubSpot API throughout Phases 0–4. Access must remain active until cutover is confirmed stable.

→

Tyler + Lia AvailabilityUAT Waves 1 and 2 require hands-on time during June. Pre-schedule review sessions from day one to prevent timeline slip.

Plan F — proposed under a revised budget of $20K/month for 3 months (June–August). Trade-off vs. the prior 5-month Plan A: the full Reporting Portal build is out of scope — only the Monthly Report rollout is included. Buckets 2–4 sequencing may be refined based on learnings from the Bucket 1 delivery.

(01)Project Timeline

Bucket

June 2026

July 2026

August 2026

September 2026

Wk 1

Jun 1–7

Wk 2

Jun 8–14

Wk 3

Jun 15–21

Wk 4

Jun 22–28

Wk 5

Jun 29–Jul 5

Wk 6

Jul 6–12

Wk 7

Jul 13–19

Wk 8

Jul 20–26

Wk 9

Jul 27–Aug 2

Wk 10

Aug 3–9

Wk 11

Aug 10–16

Wk 12

Aug 17–23

Wk 13

Aug 24–30

Wk 14

Sep 1–7

Wk 15

Sep 8–14

Wk 16

Sep 15–21

Wk 17

Sep 22–28

Bucket 1A · ✓ DoneEDI Order ExtractionHaziq Khurshid · Shipped May 2026

✓ All 3 EDI Platforms Complete — Spring Systems · Bamboo Rose · SPS Commerce — Shipped Ahead of Schedule

Track A — Order Entry → Billing

Bucket 1BCamelot Write-Back + Auto-TriggerTrack A · Camelot API · Gmail Watcher

Bucket 1B — POs → Camelot + Gmail Watcher · Jun 1–21

Bucket 4 · PilotBilling Engine — MetacineTrack A · Box Selection · Compute Charges

Bucket 4 — Billing Engine · Metacine Pilot · Jun 22 – Aug 2

Bucket 4 · RolloutBilling — All Brands ConfigTrack A · DataStudios + Danny Castro

Bucket 4 Rollout — All Brands · Aug 3–30

Track B — Transport → ASN

Bucket 3Transportation & RoutingTrack B · TechShip · Nordstrom TMS · Bluemercury

Bucket 3 — TechShip (Jun 1–21) · Nordstrom TMS (Jun 15–Jul 12) · Bluemercury (Jul 6–26)

Bucket 2Shipment & ASN AutomationTrack B · Spring Systems · Bamboo Rose

Bucket 2 — ASN 855/856 · Spring Systems (Jun 29–Jul 26) · Bamboo Rose (Jul 13–Aug 16)

September — Hardening & Validation

HardeningException Handling + Per-Brand ConfigDataStudios · All Buckets · Sep 1–14

Hardening — Exceptions · Edge Cases · Billing Config · Sep 1–14

Dry RunPre-Production ValidationDataStudios · Danny Castro · Rita Murillo

★ Danny + Rita Sign-Off · Sep 15–28 · Q4 Ready

Already Complete

Active Build

Rollout / Extension

Hardening

★ Q4 Ready Gate

(02)Key Milestones

June 1, 2026

Access Gate

All system credentials in hand: Camelot API auth, EDI portal logins, Nordstrom CTE portal. TecOMS decision confirmed. Email forwarding live. Product dimension collection started by Danny.

June 21, 2026

Bucket 1B Live

EDI purchase orders writing directly to Camelot via API — end-to-end loop closed. Gmail watcher auto-triggering extraction on inbound EDI notification emails.

July 26, 2026

Routing Live

TechShip labels auto-generated via Techdinamics API. Nordstrom CTE routing request submitted automatically. MATM# parsed from approval email. Label data machine-readable — ASN unblocked.

Mid-July 2026

Dimensions Deadline

Product dimensions + weights for all active SKUs must be loaded in Camelot. Owner: Danny Castro + brand contacts. Hard deadline — billing engine cannot compute charges for brands missing dimensions.

August 16, 2026

ASN Live

EDI 855 + 856 auto-populated for Spring Systems and Bamboo Rose retailers. EDI 810 invoice auto-fires on ASN send. Zero manual portal data entry for covered retailers.

August 30, 2026

Billing Engine Live

Camelot Compute Charges auto-triggered on shipment completion. Supply line items auto-populated for all brands with dimensions loaded. Metacine pilot validated; all brands configured.

September 15, 2026

Dry Run

End-to-end dry run across all clients, all buckets with Danny and Rita present. Automated output validated against known-good manual output. All edge cases resolved.

September 30, 2026

★ Q4 Ready

Full system signed off by Danny Castro and Rita Murillo. All four buckets live. System stable before October holiday order volume hits — Q4 does not crumble this year.

(03)Critical Dependencies

→

Access Gate → EverythingAll system credentials and the TecOMS decision must land by June 1. No engineering work starts on any bucket without credentials. This is the single gate to the entire plan.

→

Bucket 3 → Bucket 2ASN automation (EDI 855 + 856) requires machine-readable label data — UPS tracking numbers generated programmatically by TechShip API. Bucket 2 cannot start until Bucket 3A is live.

→

Product Dimensions → Bucket 4Billing engine requires SKU-level dimensions + weights loaded in Camelot. Danny Castro must drive collection from all brands by mid-July. No code workaround exists.

→

Camelot API Auth → Bucket 1BCamelot API endpoints are confirmed (Danny, Session 3). Auth credentials and endpoint documentation must be delivered June 1. Camelot write-back cannot start without them.

→

Nordstrom CTE Portal → Bucket 3BCTE portal login credentials required for Nordstrom TMS automation. Must be delivered by Danny/Rita before mid-June. Nordstrom is the highest-complexity routing path.

→

Danny + Rita Sign-Offs → Each PhaseValidation at end of each major phase requires a 30-minute review. Must be pre-scheduled from day one. Blocked sign-offs prevent downstream work from starting on validated output.

(01)Project Timeline

Phase

June 2026

July 2026

August 2026

Wk 1

Jun 1–7

Wk 2

Jun 8–14

Wk 3

Jun 15–21

Wk 4

Jun 22–28

Wk 5

Jun 29–Jul 5

Wk 6

Jul 6–12

Wk 7

Jul 13–19

Wk 8

Jul 20–26

Wk 9

Jul 27–Aug 2

Wk 10

Aug 3–9

Wk 11

Aug 10–16

Wk 12

Aug 17–23

Wk 13

Aug 24–30

Wonder Valley · ✓ DoneMonthly ReportLive in portal · May 2026

✓ Wonder Valley — Live in Reporting Portal · May 2026

Phase 0Brand AuditHaziq · Tyler · Jun 1–14

Brand Audit — Retailer Matrix per Brand · Jun 1–14

Fast Track — Existing Adapters

Fast Track · ACarbon Beauty GroupSelf Glow · Sweed · Reverie · Already in Pipeline

Carbon Beauty — Portal Config + Verification · Jun 8–28

Fast Track · BConfig-Only BrandsScope confirmed after audit · Jun 15–Jul 12

Config-Only Brands — TBD from Brand Audit · Jun 15–Jul 12

Slow Track — New Retailer Integrations

Slow Track · ANew Adapter BuildsNew retailer portals · Scope from audit

New Retailer Adapter Builds · Jun 15–Jul 26

Slow Track · BBrand RolloutConfigure + deploy after adapters built

Slow Track Rollout · Jul 20–Aug 16 · ★ Mid-Aug Target

Onboarding — New Brand

CalecimNew Brand OnboardingPending Tyler's signal · ~August 2026

Calecim — Brand Onboarding · ~Aug 3–23

Already Live

Active Build / Config

Scope TBD / Pending

New Integration Work

Audit Gate — Jun 14

Full Rollout — Mid-Aug

(02)Key Milestones

June 1, 2026

Brand Audit Begins

Tyler confirms which retailer portals each brand sells through. Haziq maps against existing adapters. Carbon Beauty brands enter final portal config in parallel.

June 14, 2026

Audit Gate

Brand × retailer matrix complete. Fast track confirmed: brands using only existing adapters. Slow track scoped: brands needing new integrations and estimated build time.

June 30, 2026

Fast Track Complete

Wonder Valley, Self Glow, Sweed, Reverie, and all config-only brands operational. Tyler's manual Canva process replaced for these brands.

Mid-August 2026

★ Full Rollout

All 14 active brands live in the reporting portal. Tyler no longer building Canva decks manually. Reports are CRM-integrated, so rollout follows the mid-July cutover. Confidence depends on adapter complexity discovered in audit.

In Pipeline — May 2026

Carbon Beauty Group

Self Glow, Sweed, and Reverie already configured in ingestion_config.yml. Sweed also has Nordstrom S3 adapter. Fast track brands — portal verification only.

TBD — After Jun 14 Audit

Config-Only Count

Brands that sell only through Revolve, Nordstrom, Google Drive, or Gmail sources can be configured without new adapter work. Likely 3–5 additional brands.

TBD — After Jun 14 Audit

New Adapter Scope

Brands selling through retailers with no existing adapter require new integration builds. Each new retailer: 1–2 weeks. Determines the mid-August confidence level.

~August 2026

Calecim Onboarding

New brand currently onboarding. Tyler to signal when ready. Follows same onboarding pattern as other brands once retailer mix is confirmed.

(03)Key Dependencies

→

Brand Audit → Fast / Slow SplitThe June 14 retailer matrix is the gate that determines which brands are config-only vs. require new adapter builds. Tyler's input is the single external dependency.

→

Adapter Complexity → Mid-Aug ConfidenceIf the audit reveals 5+ brands requiring new retailer integrations, the mid-August full rollout target may shift. Each new adapter is 1–2 weeks of build work.

→

CRM Database → All BrandsPipeline / deal data for all active brands is already in the portal database. No HubSpot dependency — the reporting portal reads CRM data directly from the shared DB.

→

Carbon Beauty S3 → Self Glow / Sweed / ReverieThese three brands are already configured in ingestion_config.yml with the Carbon Beauty S3 adapter. Fast track work is portal verification only.

→

Tyler's Signal → Calecim StartCalecim is actively onboarding and not yet in the CRM. Tyler will signal when the brand is ready (~August). No blocking dependency on the main rollout.

→

Wholesale Goals (Google Sheets) → Each BrandEach brand's monthly goal data lives in a separate Google Sheet. Tyler or each brand's sales manager must confirm the Sheet ID per brand before the portal can display the sales vs. goal chart.

(04)Brand Rollout Scope

✓ Live in Portal

Wonder Valley

Fast Track · June 30 Target

Self Glow by James Read

Sweed

Reverie

Pending Brand Audit · Mid-Aug Target

Ancient + Brave

Basics by B

Glasshouse Fragrances

HUE

Juvenate

Orb Oils

PopSockets

Qure Skincare

Rituel de Fille

Sarelly

Coming Soon · ~August

Calecim

Not in Scope

Mienne