Shopify Sync (Products, Inventory, Orders): What’s Where

Why this page exists (for SDRs)

Ribbn’s Shopify integration is designed to reduce operational risk for resale businesses by keeping Ribbn as the system of record for inventory + product truth, while using Shopify as the online storefront for publishing and managing online orders.

In discovery, your job is to quickly confirm:

• What the prospect expects Shopify to “own” (products, inventory, orders), and
• Whether they’re comfortable with Ribbn-first workflows (critical for multi-seller/consignment, one-of-a-kind inventory, and payout clarity).

The rule of thumb: “Ribbn first, Shopify for storefront + online orders”

Ribbn = source of truth

Use Ribbn for:

• Inventory & lifecycle status for one-of-a-kind and variant items
• Product setup & edits (title, description, pricing, media, taxonomy-like fields)
• Multi-seller/consignment mapping (seller tied to items, commissions)
• Operational controls (holds, QC statuses, sold-state behavior)
• In-store checkout (Ribbn POS: app POS / web POS) and in-store returns

Shopify = online storefront + online order ops

Use Shopify for:

• Making synced products visible online (status Draft → Active)
• Online orders: fulfillment, refunds, online returns
• Storefront setup like theme/design, navigation/menu, and collections

What’s where (Products, Inventory, Orders): quick reference

Responsibilities by area (SDR-ready)

What actually syncs from Ribbn → Shopify (and why it matters)

When a merchant selects items in Ribbn and publishes/syncs to Shopify, Shopify receives:

• Core product data (title, description, price)
• Media (images)
• Additional Ribbn attributes transferred as Shopify Meta Fields (commonly used for filtering/search, building collections, and merchandising rules)

Examples of Ribbn data that shows up in Shopify as Meta Fields

Use these as discovery anchors to explain why “Ribbn-first” helps resale ops:

• Taxonomy-like fields (segment/category/type/style)
• Size fields (standard/label size)
• Brand, color, condition, original price
• Commission + seller identifiers (seller name, Ribbn seller ID)
• Inventory location(s), tags, RFID
• Ribbn status/product class (e.g., UNIQUE), Ribbn item IDs/references

Inventory & status mapping: the #1 “gotcha” to qualify early

The risk: Ribbn status changes do not automatically “unpublish” in Shopify

If a product is moved in Ribbn to a non-sellable operational state (QC, repair, hold, etc.), the team must ensure Shopify availability matches reality.

How merchants prevent accidental sales online:

• Set the Shopify product back to Draft, or
• Remove it from Shopify

What happens when something sells in-store (important for omnichannel trust)

When an item hits a Sold-state in Ribbn:

1. Shopify inventory quantity decreases automatically
2. When inventory reaches 0 (often immediate for one-of-a-kind items), the Shopify product is set to Draft
3. The item is effectively removed from online sale

Why SDRs should care: This is a core “operational trust” story—Ribbn helps prevent overselling for unique inventory across in-store + online.

Publishing flow: what SDRs should explain (light technical)

High-level workflow (sound-bite version)

1. Create/edit in Ribbn
2. Sync/publish from Ribbn to Shopify
3. In Shopify, item appears as Draft
4. Merchant sets to Active when ready to sell online

Variants (sizes/colors): what to know

If a merchant needs variants (size runs, multiple colors):

• Variants are configured in Ribbn first and map to Shopify’s variant structure.

Route deep “how do we build variants exactly?” questions to AE/SE or Support Hub.

Orders: what “sync” means (and what it doesn’t)

Online orders live in Shopify

• Online orders are created and managed in Shopify.
• Ribbn may show Shopify order history because orders are mapped into Ribbn, but they are view-only there.

In-store sales/returns stay in Ribbn

• Ribbn remains the in-store POS and in-store ops hub (sales + returns), typically tied to Ribbn/Stripe.

Discovery questions (to reduce Shopify confusion fast)

Use these to qualify fit and avoid integration surprises.

System-of-record alignment (must-have)

1. “Where do you want your team to create and edit products day to day—Shopify or Ribbn?”
2. “Do you sell one-of-a-kind inventory, or do you rely heavily on variants?”
3. “How important is it that the same item can sell in-store and online without overselling?”

Resale/consignment workflows (Ribbn value narrative)

1. “Are items owned by the store, or do you run consignment / multi-seller?”
2. “Do you need seller mapping, commissions, and payout clarity per item?”
3. “Do you need seller-facing workflows like sell requests or self payout (vs fully manual payouts)?”

Operational trust drivers

1. “Do you use operational statuses like QC/repair/holding periods—and do you expect those to affect online availability?”
2. “How do you handle returns online vs in-store today?”
3. “Any compliance requirements like GDPR deletion expectations?” (Keep this high-level; route specifics.)

Omnichannel & platform setup

1. “Is Shopify your current storefront, or are you planning a migration?”
2. “Who will own building Shopify theme/navigation/collections—your team or an agency?”

Talk tracks (SDR-ready)

1) “What’s where” in one breath

“Ribbn is your resale operations engine—inventory, intake, seller commissions and payouts, and in-store POS. Shopify is the storefront: we sync products into Shopify for online publishing, and Shopify is where online orders get managed.”

2) Handling the “Can Shopify be the source of truth?” objection

“If Shopify is where you want to manage product truth, Ribbn won’t be a fit operationally—our model is Ribbn-first so one-of-a-kind inventory, seller attribution/commission, and lifecycle controls stay clean. We can absolutely use Shopify for the storefront, but Ribbn needs to remain the system of record.”

3) Handling “Will we pay fees twice?” (guardrail answer)

“In general, in-store purchases run through Ribbn and online purchases run through Shopify—so you’re not double-charged for the same transaction. For exact fee details by plan and add-ons, I’ll loop in an AE.”

Pricing & packaging: what to say (and what not to)

SDR-safe guardrails

• Ribbn pricing is typically a combination of:
  • Plan (package level)
  • Transaction fees
  • Add-ons (e.g., RFID, extra terminals, Tradera integration)

Troubleshooting mindset (SDR-level, no deep admin)

If a prospect reports “Shopify is wrong” or “inventory doesn’t match,” ask:

• “Was the product created/edited in Ribbn first?”
• “Was it synced/published from Ribbn?”
• “Is the Shopify product still Draft?”
• “Did the item change status in Ribbn (QC/hold/sold) but Shopify wasn’t updated?”

Then: route technical troubleshooting to AE/SE or Support.

When to pull in an AE/SE (routing guidance)

Escalate when you hear:

• “We need two-way sync and want to edit in Shopify”
• “We want Ribbn lifecycle statuses to automatically control Shopify publish state without manual steps”
• “Complex variant/catalog modeling questions”
• “Order-management inside Ribbn for Shopify orders”
• “Migration project planning / timeline commitments”
• Any detailed questions about fees, payouts, or compliance guarantees

Related Support Hub references (for follow-up, not live teaching)

Shopify App (Products)

Migration / FAQ

Orders (related context)