For shops on Fulfill Engine
Your shop isn't a support ticket.
When something doesn't work the way your shop works, that's a conversation with the people who build it. Not a form. Not a queue. Not “we'll add it to the list.”
Ask for something. Get a person.
Every platform says they listen. What that means in practice is usually a form, a ticket number, and a reply that thanks you for the feedback.
Here's what it means at Riverr. You tell us something doesn't work the way your shop works. That goes to the people who build the product — not through a support tier, not into a backlog that gets triaged next quarter. If it's a real gap, we're talking about it that week. Often we're building it that week.
You won't be account #4,000.
Small enough that a call reaches the people who write the code. Big enough to run a 76-location franchise network. If your process doesn't fit the software, we'd rather change the software.
Your client's store should connect itself.
Plenty of platforms give your customers a login and a price sheet. That part isn't rare.
What's rare: your client connects their own Shopify or Etsy store to their portal, themselves, and orders start landing in your production queue. Their brand, their storefront, their customers, their checkout. You didn't rebuild anything.
We haven't seen another platform do this the same way — and we're careful not to claim nobody ever will.
YOUR SHOP (Riverr)
├── Client A portal ──── connects ──→ Client A's Shopify
├── Client B portal ──── connects ──→ Client B's Etsy
├── Client C portal ──── Riverr storefront
└── Client D portal ──── orders direct from portal
│
▼
ONE PRODUCTION QUEUENine steps, or one
Fulfill Engine (published guide)
- 1.Client Shopify must be on Grow, Advanced, or Plus — Basic is not supported
- 2.You must be the Shopify store owner to build the app in the merchant's environment
- 3.Create an app in the Shopify Partner / Dev Dashboard
- 4.Create a version; set App URL and Redirect URL to Fulfill Engine endpoints
- 5.Paste twelve API scopes exactly — mismatches cause authorization failures
- 6.Release the version and install via a pasted link
- 7.Copy the Client ID and Secret back into Fulfill Engine
- 8.Change a scope later and you must create and release a new app version
- 9.On their entry plan: contact success and add Fulfill Engine as a Staff Member inside the Shopify store
Riverr
1. Your client opens their portal and connects their store.
The sleeper detail is the plan requirement. Small clients — schools, clubs, local teams — are on Shopify Basic. Under Fulfill Engine's documented requirements they cannot be connected at all.
Want your own branded Shopify app in the app store? We can do that too.
Enterprise shops get a fully white-label Shopify app under their own brand. Clients connect the same easy way, except nothing in the experience says anything but your name — and every merchant browsing the App Store for apparel fulfillment can find you.
Fulfill Engine
Build a custom dev app — nine steps, store-owner access, Grow+ required
Riverr
Client connects from their portal
Riverr Enterprise
Client installs your app from the Shopify App Store
The order came in. Now how do you charge for it?
This is the question that decides whether connected client stores are actually useful.
An order lands from your client's Shopify. You source the blank, decorate it, pack it, ship it. Then someone works out what that client owes you, builds an invoice, sends it, chases it. Every order, every client, every week. The more stores you connect, the more of that you create.
Riverr bills it automatically. The order arrives against that client's account, at their negotiated pricing and terms, and the charge happens without anyone touching a spreadsheet. Connect a hundred client stores and your billing work doesn't change.
And on your own stores, the money splits itself.
White-label and pop-up stores run on Stripe Connect. When an order is placed, payment splits between you and the store's customer — the organizer, the school, the club, the brand — at checkout. No end-of-month reconciliation, no cutting checks after the season closes.
CLIENT'S SHOPIFY → your floor → shipped → client billed automatically RIVERR STOREFRONT → payment splits at checkout → you + organizer
Your process, not the platform's.
Every shop runs differently. Different decoration combinations on one garment. Different inserts for different licenses. Different defaults per brand. Different steps between receiving and shipping.
Most platforms have one answer to that: change how you work.
Riverr's production workflow, store settings, product configuration, and fulfillment steps are yours to shape. If your process is genuinely unusual, that's a conversation, not a rejection — the same promise as the headline, expressed as product behavior.
Fulfill Engine ends at the shipping label. Your shop doesn't.
Fulfill Engine is built for online-first fulfillment and it's good at it. But a walk-in wanting twelve tees, a local team dropping off artwork, a contract job quoted over the phone — none of those start online, and none have a home in a platform designed around webstores and API orders.
Riverr runs the front counter. The POS sale lands in the same queue as your web orders, off the same catalog, against the same inventory.
Front counter POS
Ring up a walk-in, take payment, job's in the queue before they leave.
Quote builder
Decsheets pricing matrices, multi-item quotes, approval pages, deposits.
Customer inbox
Every art revision and follow-up tied to the customer and the order.
The art department is in the software.
AI product design, image generation and editing on the customizer canvas, ghost mockups, bulk product creation, and embroidery digitizing — in the platform, not a separate subscription or a tab in Photoshop.
Embroidery digitizing availability varies by plan and rollout — we'll show you what's live on your demo.
Side by side.
| Fulfill Engine | Riverr | |
|---|---|---|
| Unlimited white-label stores | ✓ | ✓ |
| Item-level scan-to-print | ✓ | ✓ |
| Automated blank sourcing | ✓ | ✓ |
| Fulfillment network for overflow | ✓ | ✓ |
| Multi-method decoration support | ✓ | ✓ |
| Customer accounts with price sheets | ✓ (Seller Pro+) | ✓ |
| Client self-connects their own Shopify/Etsy | Custom app build, store-owner access | Client connects from their portal |
| Works with Shopify Basic clients | Grow, Advanced, or Plus required | ✓ |
| Your own white-label app in the Shopify App Store | — | Enterprise |
| Automatic billing for orders from a client's store | — | ✓ |
| Stripe Connect splits on white-label & pop-up stores | — | ✓ |
| Network visibility — who's decorating your job | — | ✓ |
| Front counter / POS | — | ✓ |
| Customer inbox + approvals | — | ✓ |
| AI design + editing | — | ✓ |
| Your own supplier accounts | Decorator Pro ($500/mo) | Every paid plan |
Based on Fulfill Engine's published pricing and feature pages as of July 2026. Something wrong? Tell us and we'll fix it.
About the fees.
Both platforms charge a storefront fee. Ours starts lower and drops faster: 3% at $199/month and 2% at $449/month, where Fulfill Engine's published rate stays at 3.5% until the $2,500/month tier. Item fees on external channels are $0.20 and $0.10 against their $0.50. Quotes carry no fee on any Riverr plan.
Per-order caps work differently between the two, so on large-ticket bulk orders the math can favor either one. Send us your last three months and we'll tell you straight.
Tell us what your shop needs.
Not a form that goes into a queue. A conversation with the people who'd build it.