Direct answer for an existing Approved model: a registered seller may add a new finish, material, size or other variant directly in the product editor. A variant-only change does not require separate Curation pre-approval. Do not ask whether the person is a seller or buyer when Vendor context is already active; treat them as the seller unless they explicitly state they are purchasing.
Registered vendor: do not use the public designer application form to propose another piece or collection. That form is only for a new designer/brand that has not yet been accepted or invited. An existing seller submits new Curation proposals in the current Vendor Dashboard chat.
Use this guide when you want to add a brand-new piece or collection, add a finish/variant to a piece already approved, or when something was uploaded before Curation selected it.
Curation is a human editorial decision. Fin can explain the process and collect a complete proposal, but it cannot approve a piece, promise selection or predict a decision date.
Choose the correct path
What you want to do | Correct path |
Propose a brand-new product/design not previously selected | Send a proposal in the Vendor Dashboard chat before uploading it. |
Propose a new collection or a group of new references | Send one structured collection proposal in chat; Curation selects the individual references. |
Add a new finish, material, size or other variant to a model already Approved | Add it directly from the product editor. Pre-approval is not required under the current policy. |
Correct the price, quantity, image or SKU of an already-approved option | Edit the existing product/variant directly. |
Change critical presentation fields on an Approved piece | Save through the normal product flow; the new version may move to Need Review. |
You already uploaded a new piece without prior selection | Do not delete or duplicate it. Share its existing dashboard link in chat for Curation review. |
1. Prepare a complete proposal for new pieces or collections
For each new piece, provide:
product/design name;
link to the piece on your website, catalogue or shareable PDF;
clear images;
materials and available finishes;
product dimensions;
intended public retail price;
made-to-order lead time or current availability/stock; and
any context that helps explain the collection, launch or relationship to your existing Oblist assortment.
For a collection, include a clear list so Curation can approve or decline each reference individually. Approval of one collection proposal does not automatically approve future unrelated products.
You do not need to build the complete Oblist listing before Curation decides. The proposal pack is shorter than the final product form, but it must contain enough visual and commercial information for a real selection decision.
2. Submit the proposal in Vendor Dashboard chat
Open the chat inside your Vendor Dashboard.
State that this is a new Curation proposal, not a technical product issue.
Share the structured information above and attach the images, catalogue/PDF or links.
If several products are involved, name each one clearly.
Wait for the Curation decision before uploading the new pieces.
Nicole/Vendor Success can receive the request and route the complete pack to Annabelle/Curation. Do not send the same proposal through several channels or create duplicate conversations.
There is no fixed public review SLA. If you need to add information, continue in the same chat rather than opening a new request.
3. After Curation approves new pieces
Upload only the references selected in the decision:
open Products → + Add Product;
choose Create Manually, Import from URL, or Shopify Sync if your store is connected;
complete all Oblist-specific fields;
save incomplete work as Draft if needed;
when complete, choose Send for review.
The prior selection and the dashboard review are related but not identical:
the proposal decides whether the piece belongs in the assortment;
the product review verifies that the actual listing is complete, accurate and ready to publish.
A pre-selected piece is therefore not automatically live after upload. It still moves from Draft to Pending, then becomes Approved once the submitted listing passes review and publication.
You do not need to send a second chat notification after Send for review unless an error, unexpected rejection or publication mismatch appears.
4. Add a new finish or variant to an Approved model
Under the current policy, a new option on a model that is already Approved can be created directly from that product's Variants section without a separate pre-approval request.
The editor supports up to two variation axes. Depending on the product setup, an option can have:
its own name;
full selling price—not a price delta;
quantity for fixed-stock inventory;
SKU; and
a photo that accurately represents that exact finish/material/size.
After saving the variant modal, also use Save and continue on the full product page. Closing the modal alone does not save the complete product.
A variants-only change is operational and does not trigger a new Curation cycle by itself. However, if the same save also changes a critical field—title, description, main gallery/video, category, condition or certain base-price settings—the product follows the normal Need Review path for that critical content.
For Shopify-linked products, keep the price source in mind: with Auto-sync prices from Shopify on, Shopify can replace base and variant prices; with it off, Oblist prices are managed manually.
5. If you already uploaded without prior selection
Do not delete the product, import it again or create another listing merely to restart the process.
If it is Draft, keep it and share its Edit URL in Vendor Dashboard chat.
If it is Pending, share the same existing link and wait for Curation's decision.
If it is Rejected, read the feedback and share the link if the reason or resubmission right is unclear.
Curation can decide from the existing submission. Duplicate listings make review and future publication harder.
6. Understand the possible outcomes
Selected: upload/complete the approved references and Send for review.
More information needed: provide the requested images, price, finish, dimensions or context in the same conversation.
Not selected now: do not upload a duplicate or repeatedly resubmit the same proposal. A later materially different collection can be proposed separately.
Dashboard feedback after upload: correct the requested listing fields and use Send for review when the button is available.
A complete product form does not guarantee editorial selection, and a Curation decision is not a technical bug. Fin must never invent why a piece was declined; only the actual Curation feedback can explain the decision.
When a teammate is required
Fin should hand over the complete proposal when:
a new piece or collection needs a selection decision;
an already-uploaded unselected piece needs a decision;
the seller requests specific rejection feedback;
a proposed product is custom, exclusive or commercially sensitive; or
the issue is a disagreement with an editorial decision.
Technical upload, validation or sync errors are separate: identify the product and error first, then route to Tech rather than asking Curation to diagnose software.