← All guides

    For suppliers

    Bringing your catalogue into Vinius

    The ways your wines get into Vinius, the integrity check every integration passes before anything is imported, the sync schedule, and what buyers see afterwards.

    Quick answer

    • Today there is one way in: the Odoo product feed, for suppliers on Odoo 19 or later with a webshop.
    • The Excel import in the Vinius format and the Vinius API come next.
    • Nothing is imported until your catalogue passes the integrity check: a test reading, a report and a spot check of ten wines.
    • After that you choose a schedule, and Vinius checks every sync again before it publishes anything.
    • Buyers who already have you as a supplier see your wines and their availability when they order from you, plus your list price excl. VAT when your feed carries a trade price.

    Where to find it

    In your Vinius portal, open Catalogue. The page shows one card per integration. The Odoo card also links to Odoo's own guide to the product feed.

    The integrations

    IntegrationSuitsKept up to date byAvailable
    Odoo product feedSuppliers on Odoo 19 or later (Odoo Online saas~18.3 or later) with the eCommerce appVinius, reading the feed on your scheduleNow
    Excel importEvery supplier, and the first load of any catalogueYou, uploading the Vinius template againComing next
    Vinius APISuppliers with a developer, another ERP or a PIMYour own systemComing next

    Odoo product feed

    Odoo can publish the products of your webshop as a product feed, in the format Google Merchant Center reads. You switch the feed on in Odoo, create one for Vinius and paste its link on the Catalogue page. Nothing is installed in Odoo and no developer is needed.

    The feed carries what your webshop publishes. Wines you keep off your shop do not reach Vinius this way.

    Step by step: Connecting your Odoo product feed.

    Excel import

    You fill in the Vinius template, one row per wine with your own product code, and upload it. Uploading again updates your catalogue. Vinius reads its own template only, not any spreadsheet layout, which keeps the check simple. It is not available yet.

    Vinius API

    Your own system (an ERP, a PIM, or a tool an agency built for you) sends your catalogue to Vinius and keeps it current. It is not available yet; the details follow when it is.

    Several at once, later

    For now you connect one integration. Later, several can run side by side: for example the Odoo feed for the wines on your webshop, and a file for the wines you sell to trade only.

    Nothing is imported before the check passes

    A catalogue that enters Vinius wrong reaches buyers wrong. So every integration starts with a quality check, called the integrity check on screen. It has three parts:

    1. A test reading. Vinius reads your catalogue exactly as a sync would, and writes nothing.
    2. The report. Counts first, then six checks on the catalogue as a whole, then the findings on single products, each with the products it concerns.
    3. The spot check. Ten random wines as Vinius read them. You mark each one right or wrong. A single wrong wine means the reading needs fixing before you can schedule anything.

    All six checks must pass: the feed can be read, it has products, no more than 5,000 of them, every SKU appears once, at least half of the products are wine, and at least 90% of the wines are complete.

    A finding on one product affects that product only. It is left out, set aside as not wine, or published with a warning. You fix what the report finds at the source, in Odoo, and run the check again.

    Every check and finding, with its fix: The integrity check, check by check.

    The schedule

    Once the check has passed and the spot check is confirmed, you choose when Vinius reads your catalogue:

    • Daily, or Weekly on a day you pick
    • at an hour you pick, Brussels time

    Activate and sync now starts the first sync straight away, whatever the schedule says. After that the schedule takes over. Sync now reads your catalogue at any other moment, and Pause stops the syncs until you resume them.

    There is nothing faster than daily. Odoo refreshes its feed about once a day, so reading it more often would read the same file.

    Every sync is checked again

    Each sync runs the same checks as the first. A sync that changes much more than usual is held before anything is published:

    • more than a fifth of your wines would disappear
    • more than a quarter of the prices change
    • one price moves by more than half

    You look at the report and choose Apply anyway or Discard. Until you do, buyers keep seeing the previous state.

    Wines that leave your catalogue are no longer listed. Vinius deletes nothing: when a wine comes back, its offer is listed again.

    What happens after a sync

    Vinius links every wine in your catalogue to its shared wine catalogue:

    • A wine and vintage Vinius already knows is visible to buyers as soon as the sync is applied.
    • A new vintage, or a wine new to Vinius, is added to the Vinius catalogue, checked and enriched. Buyers see it once enrichment is done, or 24 hours after the sync, whichever comes first.
    • A wine Vinius cannot place with certainty is not published. The report lists it under To review.

    Your catalogue never creates stock in a buyer's account, and it never sees their orders.

    What buyers see

    For now, your catalogue reaches the buyers that already have you in their supplier list. When one of them creates an order for you and adds a wine, your wines appear above the rest of the Vinius catalogue, each with its bottle size, its availability and your list price excl. VAT. Picking one fills in the bottle size and the price, less any discount the buyer has recorded for you.

    Only the people allowed to see purchase prices in that buyer's account see your price. And a price only appears when you declare that your feed carries a trade price. Otherwise prices come per order.

    Related guides