Direct-to-consumer apparel
A DTC apparel operator running five brand Shopify stores — each with its own Shopify Payments account, its own fulfillment rules, its own return policy — decided to consolidate two months before Black Friday. Here's the 10-day cutover that didn't blow up BFCM.
The numbers, side by side
Before multiflow
After multiflow
The full story
The operator runs five DTC apparel brands — a women's athleisure line, a men's streetwear brand, a hiking and outdoor brand, a kids' line licensed off the athleisure brand, and a recently-launched recovery-wear brand targeting runners. Total portfolio revenue runs about $3.8M/yr on a strong year.
Each brand lives on its own Shopify store with its own Shopify Payments account. This is the Shopify-native way to do multi-brand. It works mechanically — Shopify gives you 5 dashboards, 5 Payments accounts, 5 payout schedules, 5 sets of tax rules. What it doesn't give you is any consolidated view of the business you're actually running, which is one operator with five brands.
The founder was spending 38 hours a week in Shopify dashboards — not doing merchandising, not doing creative, not doing vendor negotiation, just dashboard work. Pulling daily sales reports, reconciling payouts against her bank, answering refund requests via five separate customer-service inboxes, and chasing down the 12 or so inventory-sync conflicts that happened every week when two of her brands sold overlapping SKUs (the athleisure and the recovery-wear shared three base items).
Refunds were the worst of it. Each brand had its own Shopify Payments payout schedule — some daily, some on a 3-day rolling. A customer who wanted a refund on the hiking brand and the athleisure brand in the same order (which happened, because the same customer bought across brands) would wait 3–5 business days for each refund to clear, on different timelines. CX was fielding increasingly angry "where is my refund" emails.
Black Friday 2023. The athleisure brand — the flagship — ran a viral Instagram-influencer campaign that drove a $180k sales spike in 18 hours. Shopify Payments' fraud system read the spike as suspicious (legitimately — the traffic pattern matched bot-driven credential stuffing in Shopify's model), paused the account, and held payouts pending review.
The freeze lasted 72 hours. During those 72 hours the brand was still capturing charges at checkout, but no money was flowing to the operating account. The founder had $220k in weekly payroll and a $40k ad spend commitment that Monday. She ended up borrowing from her personal line of credit to cover the gap.
The account unfroze and the held payouts released. But she'd spent BFCM weekend on the phone with Shopify risk agents instead of shipping. The recovery-wear brand, which she'd planned to soft-launch that weekend, got pushed to Q1.
She decided the following quarter: never again. The path she'd been taking — opening a new Shopify store for every new brand — was creating five independent risk profiles that each individually got pulled at inopportune moments. A friend who ran a peptide portfolio mentioned multiflow in a Slack group for multi-brand operators. She spent an afternoon on the site and booked a call.
Timing was the hard constraint. The operator wanted cutover done by late September to have six weeks of runway before BFCM 2024 in case anything went sideways. Underwriting review (Shopify Payments' parent underwriting, which multiflow sits on top of) came back clean in 48 hours.
Day 1–2: Store inventory and descriptor mapping. All five brands kept their Shopify-native checkout and their Shopify Payments acquirer relationship. What moved to multiflow was the orchestration layer — consolidated webhook stream, unified payout view, centralized refund flow.
Day 3–4: Apple Pay and Google Pay domain re-verification across 5 domains (handled via Shopify + multiflow's combined flow in about 40 minutes). Descriptor standardization — the recovery-wear brand had been running a generic descriptor; cleanup pushed it onto its own branded one.
Day 5–6: Refund-flow migration. This was the piece the operator most wanted. Previously refunds issued in Shopify cleared through each store's individual Payments account on that store's payout cadence. multiflow's parent-level refund handler lets refunds issue against the parent ledger immediately — customer sees the refund in their bank inside 24 hours on most card brands, same day on same-bank.
Day 7: Inventory-sync consolidation. The two brands that shared base SKUs were wired into multiflow's inventory-sync webhook so that a sale on brand A decremented inventory on brand B in under 30 seconds. Previously this had been a batch sync running every 4 hours, which is where most of the 12-conflicts-per-week problem was coming from.
Day 8: Test transactions across all five brands. 25 live charges, 10 refunds, 3 dispute simulations. Descriptor rendering validated on iPhone statements and Chase / Bank of America / Capital One apps.
Day 9: Cutover webhook URLs. Five Shopify stores now stream into one multiflow parent.
Day 10: First consolidated weekly payout report landed in the operator's inbox. Five brands, one roll-up, one reconciliation pass.
The thing I underestimated was how much of my week was just Shopify dashboard tab-switching. Five Shopify admins, five Payments dashboards, five payout schedules. multiflow didn't replace Shopify — it just gave me one pane of glass for the money.
The BFCM story is the headline. BFCM 2024 processed $240k across the five brands — $60k above the 2023 spike that had triggered the freeze. Zero freezes, zero payout holds, zero risk-team calls. Not because multiflow somehow insulates from Shopify's fraud system — it doesn't — but because the volume showed up as normal traffic against a parent account with an established pattern, instead of a 3x spike on a single brand account.
Ops hours dropped from 38/week to 14/week. The 24 hours recovered went into merchandising and vendor work — the stuff the founder had been neglecting for 18 months because dashboard work was eating her calendar.
Refunds moved from 3–5 business days to same-day. This was the single most visible operational change to customers. CX ticket volume around "where is my refund" dropped roughly 80%.
Inventory-sync conflicts dropped from 12/week to about 1/week. The remaining 1 is almost always a real-time race condition on a popular SKU selling simultaneously on two brand sites, which is a feature of high-traffic moments more than a bug.
The operator is clear that multiflow didn't change her Shopify experience at the merchandising level — she still uses five Shopify admins to manage five catalogs. What changed is the money layer. The five payout files became one. The five dispute queues became one. The five refund flows became one.
She's honest about the cost: on her volume band (~$3.8M/yr, mid-Portfolio tier on multiflow's pricing) the per-transaction rate is slightly higher than what Shopify Payments was charging natively. The delta is roughly $2,100/mo. The recovered ops hours and the BFCM freeze insurance — she models that as a $50k annual tail-risk event she's no longer carrying — more than cover the delta.
Her quote above is the one she wanted in the hero.
The operator is clear that multiflow didn't change her Shopify experience at the merchandising level — she still uses five Shopify admins to manage five catalogs.
More operator stories
Adult creator content
A boutique adult content platform representing 10 creators — models with individual subscription bases on the platform's own white-label storefronts — spent…
Read the story →Subscription commerce
An operator running 11 niche subscription box brands — from meal-prep to pet treats to craft beer to teenager-subscription-gift — had 11…
Read the story →SARMs research chemicals
A 12-brand SARMs research chemical operator who'd been declined by seven major acquirers (Stripe, Square, Authorize.net, PayPal, Braintree, WePay, Adyen) in the…
Read the story →Most operators are approved inside 48 hours. 12 questions, no hard-pull, no obligation.
Talk to an operator
Human reply within 2 business hours. No chatbot.