VTEX Architecture · Draft v1

Arbonne International — Direct-Selling Commerce Platform

Solution architecture drafted for the RFP demo / deep-dive workshop track. Pink = VTEX-native modules, gray = Arbonne's existing third-party systems being kept, red dashed = systems being decommissioned. Interface details and open assumptions are documented below the diagram.

Markets6 markets · 8 bindings

Scale~$274.8M ARR · ~120K orders/mo

Hard deadlineSAP CC contract exp. Oct 2027

WAF (VTEX) OOTB — perimeter security, DDoS/bot protection

VTEX CDN Edge · cache · TLS 1.3 — storefront / webview traffic

Customer & consultant entry channels

Storefront (FastStore)

6 countries

4 languages

Guest journey

Consultant-replicated

Recommended Cart

Price Table Selection

Arbonne Commerce Platform — VTEX Account

VTEX Core Modules

VTEX IDAuth · SSO for VTEX and external systems

Catalog

Catalog Translations Multi-language

PricingGuest / PC / VIP / IC price tables

Promotions Stacking, sponsor rules · non-QV only

Loyalty

Intelligent SearchReplaces Solr

CMS & Localization6 markets · 4+ languages

Commercial Policies4-tier pricing per country — Guest baked into the policy + PC/VIP/IC tables

CX PlatformPre-order consultant content assist (images/audio) + post-purchase CSR return/change flows open

Direct-Selling / MLM Commerce

Sponsor AttributionReplicated sites open

Guest Attribution"Pending Assignment" CID=1

Consultant Locator (Custom)Search IC by zip/name/rank

Onboarding Flow3 enrollment paths (Guest, PC, IC)

Promotions QVAny promo condition involving QV routes here instead of the native engine

Transactional modules

CheckoutGuest, split pay, 3DS UK/PL

SubscriptionsReplenishMe / Autoship

Order / ASM Queues12+ queues, 20+ reason codes · primary CSR console

Inventory SyncReal-time OOS/backorder

Event Fulfillment Pre-allocated stock, pickup logistics

POS / Event Cart GTC events

ReturnsRMA, refund workflow

Payment · fraud · tax connectors (kept vendors, VTEX App Store connectors) REF-10…14

VertexTax engine

SignifydFraud · OOTB via Antifraud Provider Protocol

BlueSnapPSP · tokenized vaulting evaluate

KlarnaBNPL · OOTB payment method

SmartyStreetsAddress validation

Apple / Google Pay+ BLIK candidate (PL)

Direct platform integrations (new — direct with the VTEX Account, not via Boomi) REF-15

GA4 Kept — already implemented, history preserved

Boomi Kept as orchestration / iPaaS layer for corporate systems ownership model open

Corporate systems (via Boomi)

Exigo MLM genealogy & commissions · RV/QV/CV calc consumed every ~2 min · payout via HyperWallet (US/CA), direct bank (AU/NZ/PL/UK)

Oracle EBS WMS, inventory, shipping, order fulfillment

OneTrust Consent mgmt — new, replaces SAP CDC; must migrate consent history

AWS Redshift / Fivetran / dbt Data lake & warehouse — push not just pull (REQ-037)

Carrier APIs UPS, FedEx, Canada Post, Australia Post

Marketing data feed REF-24

↓ AWS Redshift / Fivetran / dbt Salesforce Marketing Cloud Marketing/messaging — fed by the warehouse pipeline, not Boomi. No direct VTEX interface. open

Decommissioned

SAP Commerce Cloud (Hybris / ACE)Replaced by VTEX Account

SolrReplaced by VTEX Intelligent Search

SAP CDCReplaced by OneTrust + VTEX identity

SAP S/4HANAGL & financial reporting — replacement system TBD

Entry channels

VTEX-native modules

Integration layer (Boomi)

VTEX Account layer

Arbonne's existing systems (kept)

Decommissioned this migration

Interface descriptions

Each diagram tag maps to a card below: what's exchanged, which system owns it, and what is still open per the RFP.

Entry channels → VTEX

How consultants, guests, and event shoppers reach the platform.

REF-01

Storefront (FastStore) → VTEX Account

VTEX: Storefront · Sponsor Attribution · Guest Attribution · Commercial Policies · Checkout — one storefront, 8 bindings (language + currency)

→ Guest checkout, no consultant selected (lands on "Pending Assignment" CID=1 if entering via arbonne.com directly, or attributed to a specific IC if entering via that IC's slug) → Personalized/replicated experience per consultant via slug + sponsor cookie, on the same storefront ← IC-tier pricing, Favorites, Recommended Cart Attribution persists across login/logout; if a shopper clicks Consultant A's link but checks out via Consultant B's, B gets credit. Guest customers can also choose a consultant on a later order.

REF-05

WAF (VTEX) → VTEX CDN → VTEX Account

VTEX-native WAF, OOTB, fronts perimeter security; VTEX CDN fronts the Store Framework origin

→ HTTPS routed + session, TLS 1.3 minimum ← SSR / static assets

Native payment · fraud · tax connectors

Kept vendors, integrated as native/App Store connectors rather than through Boomi.

REF-10

Checkout → BlueSnap

VTEX: Checkout · Subscriptions

→ Card auth / capture, $0-auth vaulting (Create Vaulted Shopper) for saved cards & ReplenishMe tokenized billing ← Auth/capture result, chargeback events (via Chargeback911) Up to 3 saved cards, up to 6 payment methods split per order VTEX Subscriptions requires the PSP to support tokenized-card + merchant-initiated recurring charges on VTEX's connector specifically — confirm BlueSnap's VTEX connector supports this before assuming it works out of the box; if not, a second PSP would be needed for ReplenishMe only Evaluate whether BlueSnap needs to remain a dedicated, separately-maintained PSP long-term, or whether VTEX's native payment stack / another certified gateway can consolidate this role

REF-11

Checkout → Signifyd

OOTB via VTEX: Antifraud Provider Protocol — VTEX's native connector framework (same family as the Payment Provider Protocol); Signifyd plugs in as a certified connector, same API/webhook contract as today

→ SALE API (submit for fraud evaluation), Record Return API, REFUND API ← Webhook "Decision Made" (approve/decline + score), Webhook "Case Review" (manual review outcome) Async queue: SLA 4h, typical response 1–1.5s; declines route to CSA manual review in Signifyd Console; not integrated with Exigo

REF-12

Checkout → Vertex

VTEX: Checkout — tax calculation by market

→ Taxable amount request by shipping address / market rules ← Tax/GST amount; VAT-inclusive pricing configured in the commerce system for international markets

REF-13

Checkout → Payment methods (Klarna, Apple Pay, Google Pay, BLIK)

Klarna is OOTB as a native VTEX payment method — 150+ payment-provider connectors available

→ Klarna required in all 6 markets; Apple Pay/Google Pay/CC everywhere BLIK (Poland) requested as an open enhancement beyond current method set Confirm whether Klarna processes directly as a native VTEX payment method or is routed through BlueSnap as the underlying gateway

REF-14

Checkout → SmartyStreets

Real-time address validation at checkout — native, VTEX-certified connector, replacing PostGrid

← Validated/normalized address

Direct platform integrations new

GA4 connects straight to the VTEX Account — no Boomi hop.

REF-15

VTEX Account → GA4

Web analytics — kept, already implemented on the current site

→ Page/event tracking, direct from the storefront (no Boomi hop) Historical data preserved/migrated; separate prod/non-prod tracking containers

CSR & back-office

Customer-service visibility for the direct-selling model.

REF-30

CSR console → Order / ASM Queues

VTEX: Order / ASM Queues — native ASM is the primary CSR console (12+ queues, 20+ reason codes)

Impersonation (CSR/admin view-as-shopper) was removed from initial scope — "shop as customer" support for CSR is currently out of scope / open Native ASM/back-office screens will not reflect Exigo's true commission/genealogy state unless the bridging layer flagged in REF-21 is built — mandatory scope for CSR to have accurate data, not a nice-to-have

Integration layer

Boomi remains the orchestration layer between VTEX and Arbonne's corporate systems.

REF-20

VTEX Account → Boomi → Corporate systems (REF-21…27)

Transversal for Exigo, Oracle EBS, OneTrust, data pipeline. Not used by REF-01…15 (native/direct connectors) — GA4 now integrates directly (REF-15), bypassing Boomi.

→ GET/POST/webhooks All core integrations (EMS, Oracle, Boomi, Signifyd, BlueSnap, Fivetran) must also exist in test/staging per RFP

REF-21

Exigo — MLM genealogy & commissions

VTEX owns the shopping experience; Exigo keeps genealogy/commissions/back-office reporting

POST → Order, RV/QV/CV (calculated in the commerce system at order time, proportionally reduced by promos), returns/clawback data ← Consultant status (active/terminated) pushed to profile — no real-time call during shopping Data flows to Exigo every ~2 minutes; final statement only after Exigo's month-end close; payout via HyperWallet (US/CA, SFTP), HSBC (AU/NZ/PL), Bank of America (UK) Exigo itself may be a separate RFP track — ownership/scope split to confirm Native ASM/back-office screens will not reflect Exigo's true commission/genealogy state unless a bridging layer is built — treat this as mandatory scope, not a nice-to-have, or CSR-facing data will be misleading

REF-22

Oracle EBS — fulfillment, WMS, inventory

VTEX: Inventory Sync · Order / ASM Queues

POST → Order for distribution/fulfillment (VTEX Order Feed/Hook — Feed must be active before the Hook can be registered) ← Inventory availability, backorder cancellation → auto-generated RMA back to commerce platform Formal OMS system-of-record boundary vs. EBS-as-fulfillment-only is unconfirmed

REF-23decommissioned

SAP S/4HANA — GL & financial reporting

Previously: order data → GL file generation. S/4HANA is now marked decommissioned in this architecture.

Legacy flow was: → Order/financial data feed for GL posting Replacement system of record for GL/financial reporting integration not yet defined

REF-24no VTEX interface

AWS Redshift / Fivetran / dbt → Salesforce Marketing Cloud (SFMC)

Marketing/messaging — abandoned cart, campaigns. Fed downstream of the data warehouse, not from the commerce platform or Boomi directly.

→ Daily batch today: customer/order/product data, pushed from the warehouse pipeline Real-time event capability for abandoned-cart/beacon tracking not yet formalized — would need to flow through the AWS Redshift/Fivetran/dbt pipeline since there's no direct VTEX↔SFMC interface

REF-25

OneTrust — consent management (new)

Replaces SAP CDC for consent/privacy management

→ Consent capture: privacy, IC agreement, Autoship agreement, communications Consent history must migrate from SAP CDC at cutover; retention window to confirm with legal

REF-27

AWS Redshift / Fivetran / dbt — data lake & warehouse

VTEX: Data & Reporting — direct read-only replica/warehouse export required, not API-only

→ Push to S3/Redshift (scheduled export or managed data share) ← Full historical order/customer data exposed at go-live; near-real-time sales metrics, hourly/daily refresh for other attributes CSR-only vs. buyer-facing exposure of historical data still undecided

Glossary

RV / QV / CV: Retail Value / Qualifying Value / Commissionable Value — SKU-level attributes used by Exigo for commission calc; must be proportionally recalculated when discounts apply.
ASM: Arbonne's order/store admin console — manages queues (On-Hold, Fraud, Cooling Off UK, Needs CSR Attention, Re-Evaluated, etc.).
CID=1 / Pending Assignment: Placeholder customer/consultant ID used when a guest checks out with no sponsor attribution.
ReplenishMe: Arbonne's Autoship / subscription program — must-have at launch, incl. self-service pause/skip/cancel and subscription reporting.
Guest / PC / VIP / IC: Four customer pricing tiers, one price table each per country: Guest (baked into the commercial policy), Preferred Client (PC discount), VIP (legacy tier, no new enrollment but still priced), and Independent Consultant (IC discount).