Quick answer
- The report is under Catalogue in the menu on the left, on the Integrations tab, below the integration's card. Owners and admins only, in the web app.
- Six checks judge the catalogue as a whole. All six must pass before Vinius enables the integration.
- Findings judge single products. A finding leaves a wine out, sets a product aside as not wine, or publishes the wine with a warning.
- Fix at the source, in Odoo, then click Run integrity check again, or answer a wine in the report: the report changes at once.
- When the report is as good as you can make it, click Submit for review. Vinius does the spot check and enables the integration.
- Every sync runs the same checks again, and a sync that changes much more than usual is held.
Open the report
Owners and admins only: managers and staff do not have Catalogue in the menu.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Below the integration's card, the report of the latest check opens with Integrity check passed or Integrity check not passed, the counts and the six checks.
- To see an earlier check or sync, click it under Checks and syncs. Back to the latest returns to the latest one.
In the app
Not in the app: use the web app.
Below the checks come the findings and the list of products. Each finding is a filter: click it to list the products it concerns, with their Product code, the name In the feed, what Vinius Read as, and the Result. Click a count, such as New wines, to list its products. When a finding is open, the link above the list, for example How to fix "Vintage unclear", opens its section of this guide.
Left-out findings come first, largest at the top. Start there: they decide whether 90% of your wines are complete.
When wines wait for you, the list opens on Needs your answer: the wines an answer on the Integrations tab settles. Fix in the feed lists the ones only a change in Odoo can fix. Name to check holds the wines waiting only because their name is not clean enough. Read as also names the style Vinius read, so a rosé Champagne read as a still rosé stands out.
| Count | What it counts |
|---|---|
| Products read | Every product in the feed |
| Wines | Every product except the other items and the ones set aside as not wine |
| Matched | Wines Vinius already knows, vintage included |
| New vintages | Wines Vinius knows, in a vintage it does not have yet |
| New wines | Wines new to Vinius |
| Uncertain | Wines that look like one Vinius knows, without certainty |
| Left out | Wines a finding leaves out |
| Set aside | Products set aside as not wine: spirits, beer, vouchers, tastings and the like |
| Other items | Glassware, decanters and other items. Counted, but not published |
| With list price | Wines with a list price Vinius will use |
Answer the wines that wait for you
Owners and admins only.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Click Show the 3 wines that need your answer on the integration's card (the button shows your number), or Needs your answer above the list.
- On each wine, click the answer that fits: the wine Vinius proposes (It's and the wine's name), Different wine, a producer (Use and its name), New producer, This is right, add it, Correct producer or wine name or Leave out.
- The report moves on to the next wine by itself. Next wine to answer does the same at any moment.
In the app
Not in the app: use the web app.
On the latest check each answer takes effect at once: the wine's result, the counts and the six checks change straight away. On a sync, an answer takes effect from the next sync. Show all products shows the whole reading again once every wine has its answer.
Give several wines one answer
Owners and admins only.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- In the list of products, tick the rows of the wines, or the box at the top to select the whole page.
- In the bar above the list, click Leave out, This is right, add it, Use the names as read or Same producer for all.
In the app
Not in the app: use the web app.
For the wines waiting only for their name, Use the names as read above the list shows their number, for example Use the names as read (12). It first lists those wines, so you can check them, and the same button then uses each name as Vinius read it. All products shows the whole reading again.
Correct a producer or name Vinius read wrong
Owners and admins only. Use this when the name in Odoo is right and Vinius read it wrong: there is then nothing to fix at the source.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Under the wine in the report, or under a wine Vinius sent back, click Correct producer or wine name.
- Type the Producer and the Wine name. The producer field suggests the producers Vinius knows as you type: pick one to file the wine under it, or keep what you typed for a producer Vinius does not have yet.
- When other wines were read with the same producer, tick the box Also for the other 2 wines read as Moutard (it shows your number and producer) to give them the producer too.
- Click Save correction.
In the app
Not in the app: use the web app.
For Famille Moutard | François Diligent Meunier, for example, the producer is François Diligent and the name is Meunier. When Vinius proposes a producer for a wine, the button with the producer's name and the number of wines, for example Moutard for all 3, gives all of them that producer at once.
On the latest integrity check an answer takes effect at once, also for a wine left out because no producer was found. On a sync, it takes effect from the next sync. On a feed, Read again makes the next sync read the product name afresh instead of reusing its last reading.
Leave a wine out of your catalogue
Owners and admins only. This works for a wine that is published already too.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Find the wine in the report and click Leave out on its row.
In the app
Not in the app: use the web app.
The wine is set aside, and a wine that was published is no longer offered from the next sync. Undo on the row takes the answer back.
The six checks
All six must pass. A failed check blocks the schedule, however good the rest of the report looks.
The feed could be read
Vinius opened the link and found a product feed in it. When it cannot, there is no report. You see one of these messages instead, with the steps to fix it on screen:
| Message | What to do |
|---|---|
| Odoo cannot find the feed (404). | Check that Google Merchant Center is still ticked and the Vinius feed still exists. If you deleted it, create a new one and paste its link |
| Odoo refused the link (403). | The access token is wrong, or the feed was created again with a new link. Copy the link with Copy URL and paste it into Vinius |
| The feed link was not accepted. | Copy it again with Copy URL, without changing it, and paste it into Vinius |
| The feed could not be reached. | Check that your webshop is online, then run the check again |
| The shop sends the feed link on to another address. | Check the website's domain in Odoo, then copy the link again with Copy URL and paste it |
| The link does not return a product feed. | Copy the link again with Copy URL. Vinius needs the feed's link, not a page of your shop |
| The feed is too large for one integration. | Leave categories Vinius does not need out of the feed |
| The feed has no products. | Check that the feed has your wine categories and that those wines are published |
| Not every product of the feed arrived. | Run the check again |
| Vinius could not start reading the feed. | Wait a moment and run the check again |
| Vinius did not finish reading the feed. | Run the check again |
| Reading the feed broke off before the end. | Run the check again |
Each message, with every case behind it: When Vinius cannot read your feed.
To paste a new link into an integration Vinius has enabled, click Update link. When only the access token changed, it stays scheduled.
The feed has products
The feed holds at least one product. An empty feed stops the check with "The feed has no products." In Odoo, check that your wines are published on the webshop and that the Vinius feed has its categories chosen.
At most 5,000 products
One feed holds 5,000 products at most. A larger feed stops the check with "The feed is too large for one integration." First make sure the Vinius feed has the wine categories only. If your wine list alone is larger than that, contact Vinius before you split it.
Every product code appears once
Vinius keeps track of each product by its code. When two products share a code, both are left out (Product code appears twice) and this check fails. In Odoo, give every product variant its own Internal Reference.
At least 50% of the drinks are wine
This check compares your wines with all the drinks in the feed: wine, spirits and beer. It fails when fewer than half of those drinks are wine. Glasses, accessories and vouchers do not count against it. In Odoo, open Manage feeds, edit the Vinius feed and leave the spirit and beer categories out.
At least 90% of the wines are complete
Of the products that are wine, at least 90% must be free of the findings that leave a wine out. The report shows your share next to the check. Work through the left-out findings below, the largest first.
The spot check
Counts cannot catch a reading that is wrong in the same way every time: the producer taken for the wine's name, a cuvée number read as the vintage, a magnum read as 75 cl. The spot check can.
When Vinius reviews your integration, it takes a sample of the wines it would publish, most of them new to Vinius, because a wrong reading there becomes a wrong catalogue record. For each wine Vinius compares the name in the feed with how it was read (producer, wine, vintage, bottle size and, when you declared one, the price) and with the wine it matched, and marks it right or wrong.
One wrong wine stops the integration from being enabled. Vinius then sends the integration back: the Integrations tab shows Vinius sent this integration back, the Note from Vinius and the wines read wrong, each with what Vinius read. When the name in Odoo is wrong, or the integration's settings are, fix it there and run the check again. When only Vinius's reading was wrong, click Correct producer or wine name under the wine (see Correct a producer or name Vinius read wrong above). Then click Submit again. A new check is needed only when the integration's settings changed.
Findings that leave a wine out
A wine with one of these findings is not published. The rest of your catalogue can still go live, as long as 90% of your wines are complete.
No product code
The product has no product code in the feed, so Vinius cannot keep track of it from one sync to the next. Fill in the Internal Reference of the product variant in Odoo.
No name
The product has no name, or Vinius found no wine name in it. Give the product its full name in Odoo: producer, wine, appellation, vintage.
No producer
Vinius could not tell who made the wine. Put the producer in the product name, ideally first, or add a variant attribute named Producer.
Vintage unclear
Vinius found no year, and nothing that says the wine is non-vintage. Add the year to the product name, or as a variant attribute named Vintage. For a non-vintage wine, write NV or non-vintage in the name.
When every sparkling or fortified wine in your feed without a year is non-vintage, you can turn on A sparkling or fortified wine without a year is non-vintage instead: click Edit on the integration.
A Champagne without a year is always taken as non-vintage, with or without that rule: a vintage Champagne states its year. Vinius knows a Champagne by its appellation, its region or a name that starts with the word Champagne, and reads it as sparkling, also when the name only says Rosé or Blanc de Blancs. A Coteaux Champenois, a Rosé des Riceys or a ratafia is not taken as a Champagne.
Two years in one product name
The product carries two different years, or a year next to a non-vintage marker, so Vinius cannot tell which is the vintage. Keep one year in the name. A year that is not the vintage, such as a founding year, can stay when you set the vintage as an attribute: the attribute wins over the name.
No bottle size
Vinius found no bottle size, and the rule A wine without a bottle size is a 75 cl bottle is off. Add the size to the name (75cl, 0,75 l, 1,5 L, magnum) or as an attribute named Size. Or turn the rule back on.
Style unclear
Vinius could not tell whether the wine is red, white, rosé, sparkling, dessert or fortified. Put the wine in a webshop category that names the style, such as Red wine, or add a product tag that does.
Product name not readable
Vinius could not read the product name. This can be a passing problem on the Vinius side, so run the check again first. If the same products come back every time, contact Vinius.
Product code appears twice
Two or more products in the feed share one product code. All of them are left out, and the check Every product code appears once fails. Usually two variants share one Internal Reference in Odoo: give each its own.
Products set aside as not wine
Products set aside here are not published. They do not count as wines, so they do not count against the 90% either.
Not wine
Vouchers, tastings, workshops and tickets. Vinius recognises them by words in the product name or the webshop category, in several languages.
Glassware, decanters and accessories are not set aside. They become other items, which the report counts and Vinius does not publish: see Bringing your catalogue into Vinius.
A real wine lands here, or among the other items, when its name or category contains such a word. A gift box with a wine inside is read as wine when its name carries a standard bottle size, such as 75cl. Otherwise take the word out of the name, and check that the wine does not sit in a category such as Glasses or Gift boxes.
Spirit
Whisky, gin, rum, cognac, grappa, liqueurs and other spirits. Leave their categories out of the Vinius feed.
Beer or cider
Beer and cider. Leave their categories out of the Vinius feed, as with spirits.
Case or pack
The product is a case or pack of a wine ("6 x 75cl", "doos van 6", or a bundle in Odoo), priced per case. Published as one bottle it would carry the whole case's price, so Vinius sets it aside. It does not count against the share of wine, and there is nothing to fix. List the single bottle too when venues may order it by the bottle.
Left out by hand
Someone answered Leave out on this wine in the report, so it is not published. There is nothing to fix in Odoo. To publish it after all, click Undo on its row.
Warnings
A wine with a warning is published. The warning points at something you may want to fix.
75 cl assumed
Vinius found no bottle size and took 75 cl, as the rule A wine without a bottle size is a 75 cl bottle allows. Look through the list: a magnum or a half bottle among them is now listed as 75 cl. Add the size to the name, or as an attribute named Size.
Non-vintage assumed
Vinius found no year and treated the wine as non-vintage, because it is a Champagne or because the rule A sparkling or fortified wine without a year is non-vintage is on. Check that every wine in this list really is non-vintage.
Barcode (EAN) not valid
The barcode has the wrong length or a wrong check digit, so Vinius publishes the wine without it. Correct the Barcode in Odoo, looking for a typo or a missing digit.
Barcode (EAN) shared
The same barcode is on several products in your feed, which usually means it was copied from one product to the next. A barcode names one wine in one size, so a shared one names nothing: Vinius does not link by it and does not keep it with your offers. A product that was linked by that barcode alone waits under Uncertain, with the wine it would have linked as a proposal. Give each product its own barcode in Odoo, or none.
Price not plausible
The list price in your feed is below €1 or above €5,000 a bottle excl. VAT. The wine is published without a price. It may be a price per case, a placeholder price or a typo: correct it in the feed's pricelist in Odoo. With List prices incl. VAT, check the VAT rate too, since Vinius takes it off first.
Country unclear
Vinius could not tell the wine's country from its name. A wine Vinius already knows is published as usual. A wine new to Vinius is not published without a country. Add the appellation or the region to the product name.
Product name unclear
Vinius was not sure how to read the name. A wine Vinius already knows is published as usual. A wine new to Vinius is not created on an uncertain reading: it waits under Uncertain. Check what Vinius read, then answer This is right, add it, give the right name with Correct producer or wine name, or click Leave out. A name in the order producer, wine, appellation, vintage, size reads best.
Producer unclear
The wine's name points to a different producer than the one Vinius read, for example because a Producer attribute disagrees with the name. Make the attribute and the name agree.
Same wine twice
Two products matched the same wine, vintage and bottle size. That is often right, for example a single bottle and a case of six of the same wine. If it is not, one of the two names is wrong.
Same product code, new vintage
A product code Vinius already knows now carries another year in its name. Your offer moves to that vintage of the same wine. A vintage new to Vinius is added and enriched first. There is nothing to fix, unless the year is a typo.
Same product code, another wine
A product code Vinius already knows now names another wine than the one your offer holds, for example because the code was given to a new product. Vinius does not keep the old wine under it. The product waits under Uncertain, and in a sync of your whole catalogue the old offer is no longer listed meanwhile.
Vinius only checks this when the words of the product name change. A new year or a new bottle size does not count, as each has its own finding. Nor does Vinius renaming the wine in its own catalogue: once a product name has been confirmed, Vinius does not ask again while you leave it unchanged. An offer from before 19 October 2026 may be asked about once, until its name is confirmed. When the words do change, Vinius compares the new name with the old one first. The code keeps its wine when the producer and the words that identify the wine are still there, also written as an acronym ("NPU" for "Nec Plus Ultra"). A rung, cru or dosage that appears or disappears, or another producer, is a reason to ask.
Vinius reads the product's name again, at the latest on the next sync. When it recognises the wine, your offer moves to it. When it is unsure, it asks: "This product code was … Is it still that wine?", and proposes wines, with the old one among them. If it is still the same wine, click Still followed by that wine's name; otherwise click No longer that wine. The answer holds for this product name: on a sync, it takes effect at the next sync. When the name changes again later, you are asked again.
Give every product its own code, and do not reuse the code of a product you stopped selling.
Same product code, another bottle size
A product code Vinius already knows now states another bottle size than your offer, for example 150 cl where the offer is a 75 cl bottle. A magnum is a different product for a buyer, so Vinius does not put its price on the 75 cl offer. The product waits under Uncertain, and in a sync of your whole catalogue the old offer is no longer listed meanwhile. A size Vinius assumed (75 cl assumed) never counts.
If the code now really is that size, answer It is 150 cl now (the button names the size the product states). The offer moves to that size, with the price your feed gives for it, from the next sync. If the size is a mistake, correct it in Odoo. To keep the product out of your Vinius catalogue, answer Leave out.
When you sell both sizes, give each its own product code.
The result per wine
| Result | What it means | Visible to buyers |
|---|---|---|
| Matched | Vinius knows this wine and this vintage | As soon as the sync is applied |
| New vintage | Vinius knows the wine, not this vintage. It is added and enriched | Once enriched, or 24 hours after the sync |
| New wine | The wine is new to Vinius. It is added to the Vinius catalogue, checked and enriched | Once enriched, or 24 hours after the sync |
| Uncertain | It looks like a wine Vinius knows, without certainty | No. Answer it on the Integrations tab: which wine it is, a different wine, the producer, a name to use, that an uncertain reading is right, or leave it out. On the latest integrity check the answer applies at once; on a sync, from the next sync |
| Left out | A finding leaves it out | No |
| Set aside | Not wine: spirits, beer, vouchers, tastings and the like | No |
| Other item | Glassware, a decanter or another item | No. Your catalogue in Vinius carries wine only |
On every sync
Every sync runs the integrity check again. It also compares the result with what buyers see today. A sync that trips one of these guards is held: you see This sync is on hold, and nothing is published.
| Guard | Holds the sync when |
|---|---|
| Quality check | One of the six checks fails |
| Wines left the catalogue | A large share of your listed wines would disappear |
| Prices changed | A large share of your wine prices change at once |
| One price moved | A single wine price moves sharply |
The message on screen gives the share and the limit. The disappearance and price guards look at wines only, and the share guards leave very small catalogues alone. Vinius checks the report, then publishes the sync as it stands or discards it. Until then, buyers keep seeing the previous state.
What a sync published
After each applied sync, Published shows what changed: New offers, Offers changed, Unchanged, No longer sent, Waiting or set aside, Wines new to Vinius, New vintages and Prices recorded. A quiet sync reads as quiet: an offer the sync saw without any change counts as Unchanged.
- No longer sent counts offers whose product code was no longer in your catalogue.
- Waiting or set aside counts offers taken off although the product is still in your catalogue, because it waits for an answer or was set aside. A note under the tiles says how many.
- When a known product's new price was outside the allowed range, its last price is kept and a warning says how many. Check those prices at the source: your feed, file or system.
- Lines under the tiles also say how many bottle images from your catalogue are being checked or wait for Vinius, and how many were not used and why. A wine that already has a bottle image is not counted there.
- Other items are counted apart: Items no longer listed counts the ones a sync published before.
- Syncs applied before 19 October 2026 keep their old tiles: Offers updated and No longer listed.
Not published counts the wines that passed the check but did not go live, with a reason:
| Reason | What it means and what to do |
|---|---|
| waiting for an answer | The wine is Uncertain, or its product code now states another bottle size: answer it in the report |
| country unclear | A new wine without a country. Add the appellation or the region to the product name |
| region unclear | Vinius could not place a new wine in a region it already knows. Add the appellation or the region to the product name |
| incomplete | A new wine without a producer, a name or a style. See the findings above |
| producer to confirm | Vinius may already know the producer of this new wine. Pick the producer, or New producer, in the report |
| a catalogue wine has this name | Vinius already has a wine of this producer and name that may be a different wine. Add what tells yours apart to the product name |
| product code now names another wine | See Same product code, another wine above |
| product code used by another integration | The code belongs to another of your integrations, which keeps the offer |
| product code already used by a wine or an item | The code names a wine in one place and an item in another. Give each product its own code |
| no match | Vinius could not find the wine this vintage belongs to. If it comes back on the next sync, contact Vinius |
| error | Something went wrong on the Vinius side. The next sync tries again |
| other items not published yet | Glassware, decanters and other items in your feed. Vinius does not publish them; there is nothing to do |