Ribbn Support Hub (Owwl)Ribbn Support Hub (Owwl)

Status Management (Product Lifecycle)

Overview

Status Management (Product Lifecycle) in Ribbn is a “simple but powerful” feature you’ll use daily to track products through their full journey—from seller submission to final payout.

Statuses describe where an item is in its lifecycle both physically and digitally, and they affect:

  • What actions admins can take next

  • Whether sellers receive updates at certain steps

If you’re unsure which status to use, start with DRAFT and move forward from there.

Core concept: Every product has a journey

In Ribbn, each product moves through a series of statuses that represent its stage in the lifecycle.

Two types of statuses

  1. Admin-driven statuses

    • Set manually by admins

    • Used to control the internal inventory workflow (prep, QC, listing, store availability, etc.)

  2. System-driven statuses

    • Updated automatically based on activity (for example, when an item is sold)

    • Used to reduce admin work and keep the lifecycle consistent

How products enter Ribbn: Sell Request → Inventory workflow

Products often enter Ribbn through a Sell Request submitted by a seller.

Sell Request flow (high-level)

  1. SELL_REQUEST_REVIEW
    Seller submitted a product and wants to sell it with you.

  2. ACCEPTED / REJECTED
    You approve or deny the request.

  3. SELLER_DROP_OFF
    If accepted, the seller is asked to drop off the item.

Where admins update statuses after drop-off

Once the item is physically with you, you move it into your internal workflow using Admin-driven statuses, which are available:

  • Under Product Details (the product form), or

  • Via Bulk Edit in the Action Bar (useful for many items at once)

The original article includes screenshots showing both the Product Details location and the Bulk Edit Action Bar location.

Admin-driven statuses (Inventory workflow)

After the item arrives, you manage it in the product form using the following statuses.

Statuses and what they mean

Status

When to use it

What to do here

Notes / effects

DRAFT

Start of your internal workflow

Add photos, product info, and pricing

“Start here.”

QUALITY_CONTROL

Condition review step

Check condition; add remarks if needed

Remarks are noted as “a must for online sales.”

PENDING_PUBLICATION (optional)

You want to wait before listing

Hold the item before listing

Useful as a staging step.

LISTED

Product is ready to go

Confirm it’s ready for shopfloor and/or online

Publishing example: “Listed + tag availableOnline will publish it online.”

AVAILABLE_IN_STORE

Item is on your shopfloor

Mark it as in-store only

Online effect: blocks the Buy button and marks it “Only available in store).”

HOLD

Temporary pause

Pause availability while you decide next steps

Good for exceptions or short delays.

ARCHIVED

Hide from active workflow

Remove from active visibility without deleting

Used when you need to hide products.

You can update these statuses easily from the product form in Ribbn.

System-driven statuses (Post-sale & payouts)

Some statuses are handled by Ribbn automatically based on events (for example, a sale).

Sale → payout lifecycle

  • SOLD
    Automatically set once the item is sold.

  • SOLD_SELLER_TO_BE_PAID
    Used when you manually approve payout after the return period ends (usually 14 days).

  • SOLD_SELLER_SELF_PAY
    Used when the seller handles payout themselves via the app, reducing admin work.

Payout options (choose one)

  1. Manual payout

    • Move the product to SOLD_SELLER_TO_BE_PAID

    • Arrange payment directly after the return period (typically 14 days)

  2. Self-pay

    • Move the product to SOLD_SELLER_SELF_PAY

    • Ribbn notifies the seller

    • Seller can withdraw securely using Bank ID

Only move items into payout-related statuses when you’re confident the sale is final and your store is ready for the payout step (for example, after the return period).

Bulk Edit & Action Bar groupings (managing many items at once)

In web view under All Products, admins can update multiple product statuses at once using Bulk Edit.

Statuses/actions are grouped into:

  • In-Inventory Actions

  • Clearance Actions

  • Liquidation Actions

  • Post-Sale Actions

Some actions may notify sellers—use bulk updates thoughtfully.

Key benefits (why this matters day-to-day)

Status Management helps you:

  • Organize inventory based on where items are in their journey

  • Reduce admin work with system-driven statuses

  • Keep sellers informed at the right times

  • Adapt Ribbn to your store’s workflow (including bulk processing)

Related resources (Ribbn Support Hub)

Getting started

If you’re still setting up Products & Inventory workflows, these pages are commonly used together:

  • Ribbn Support Hub (home): https://help.ribbn.ai/

  • Getting started: https://help.ribbn.ai/getting-started

  • How to create your first product: https://help.ribbn.ai/how-to-create-your-first-product

  • How Status Management works in Ribbn: https://help.ribbn.ai/how-status-management-works-in-ribbn

Product setup reference

  • Product Taxonomy system: https://help.ribbn.ai/product-taxonomy-system

  • Size Taxonomy system: https://help.ribbn.ai/size-taxonomy-system

  • Product Attribution: https://help.ribbn.ai/how-to-understand-product-attribution-in-ribbn-

Optional: Build a staff-ready workflow aid

If you want to expand this hub page, these additions pair well:

  • A process diagram (Sell Request → Inventory workflow → Sale → Payout)

  • A quick-reference checklist for staff (what status to use by scenario)