Quick answer
- In Odoo, tick Google Merchant Center in the website settings, create a feed named Vinius with your wine categories and your standard pricelist, and click Copy URL.
- The feed must carry your standard list prices, never a discounted, customer or promotional pricelist. Vinius takes each business's discount off the list price, per customer.
- In Vinius, click Catalogue in the menu on the left, go to the Integrations tab, click Connect on the Odoo product feed card and paste the link into Feed link.
- Click Save and run the check. Fix what the check finds in Odoo, or answer it in the report, until it passes.
- Click Submit for review. Vinius checks the feed, does the final spot check and enables it, and you get an email once it is live.
- Owners and admins only, in the web app. Nothing is installed in Odoo, and nothing is sent to Google.
Before you start
You need all four of these:
- Odoo 19 or later. On Odoo Online, saas~18.3 or later. Odoo shows its version under Settings.
- The eCommerce app, so your Odoo has a webshop.
- The rights to change the website's settings (website administrator).
- Your wines published on the webshop. The feed only carries published products.
Older versions of Odoo have no product feed. Without one, add your wines by hand on the Catalogue tab of Catalogue: see Bringing your catalogue into Vinius.
The first report goes faster when these are in order in Odoo:
- an Internal Reference on every product variant: your own product code
- the EAN in Barcode, where you have one
- the vintage and the bottle size in the product name, or as variant attributes
Odoo documents the feed itself in its guide to Google Merchant Center. Vinius reads the same feed, without Google.
Connect your Odoo product feed
Owners and admins only: managers and staff do not have Catalogue in the menu.
In Odoo
- Go to Website › Configuration › Settings. Under Tracking & SEO, tick Google Merchant Center and click Save. This only switches the feed on; nothing goes to Google. Manage feeds appears once you have saved.
- Click Manage feeds and create a new feed, separate from any feed you use for Google:
- Name: Vinius.
- Pricelist: the one with your standard list prices, normally the shop's default. Never a pricelist with customer, trade or promotional discounts: Vinius takes each business's discount off the list price, so a discounted price would be discounted twice. See Prices in your feed below.
- Language: the language your wine names are written in.
- Categories: your wine categories. Glassware and accessories can stay out: Vinius does not publish them. Leave out spirits too. Vouchers, tastings, workshops and tickets are always set aside.
- Click Copy URL on the new feed.
Treat this link like a password. Anyone who has it can read the catalogue it describes, so paste it into Vinius and nowhere else. Vinius stores it encrypted and never shows it again.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab, and click Connect on the Odoo product feed card. The form repeats steps 1 to 3 in short.
- Paste the link into Feed link. Vinius checks it as you paste: under the field you see Link recognised with the shop and the feed number, or what is wrong with the link.
- Under Prices in this feed, choose List prices incl. VAT or List prices excl. VAT (see Prices in your feed below). For prices incl. VAT, check VAT rate to take off (%): Vinius fills in the standard rate on wine in your country.
- Check the two rules, A sparkling or fortified wine without a year is non-vintage and A wine without a bottle size is a 75 cl bottle (see The two reading rules below).
- Click Save and run the check. Vinius reads the feed straight away and reads every product name, so a large feed can take up to an hour. When something is still missing, a grey line next to the button says what.
- Read the report. When a check fails or wines are left out, fix them in Odoo and click Run integrity check again.
- Type anything Vinius should know in Note for Vinius (optional) and click Submit for review. You can submit a check that did not pass too: say in the note what you could not fix.

In the app
Not in the app: use the web app.
Vinius reviews every integration before it publishes anything. Vinius inspects the report, does the final spot check, chooses the schedule and enables the integration, and you get an email once it is live. From then on, Vinius reads the feed every day. Until then you can keep fixing what the check finds and click Submit again.
If Vinius refuses the link, copy it again with Copy URL. Vinius accepts the link exactly as Odoo gives it: it starts with https://, points to your public webshop, ends in /gmc.xml and carries a feed_id and an access_token.
What Vinius reads
| In Odoo | In Vinius |
|---|---|
| Internal Reference of the product variant | Your product code (SKU). Without one, the feed carries Odoo's own product number, which changes if you ever recreate the product |
| Product name, with its variant | Producer, wine name, vintage and bottle size |
| Variant attributes | Vintage, bottle size and producer, when you keep them as attributes |
| Webshop categories and product tags | The style, when the name does not give it. Categories also help tell wine from glasses or gift boxes |
| Barcode | The EAN, kept with your offer |
| Stock status on the shop | Availability: in stock or out of stock |
| Price of the feed's pricelist | Your list price |
| Product images | For a wine Vinius has no photo of, the image goes to the Vinius photo review. Buyers see it once it is approved |
How Vinius reads a product name
The feed has no producer field, so most of what Vinius needs comes from the product name. It first finds the year and the bottle size (2019, 75cl, 0,75 l, 1,5 L, magnum), then splits the rest into producer and wine name, and recognises the appellation, the country and the style.
Names that start with the producer and carry one year and one size read best, for example Producer Wine Appellation 2022 75cl. For a non-vintage wine, write NV or non-vintage in the name.
An attribute gives Vinius the answer directly. An attribute for the vintage or the size wins over the name. Vinius recognises attributes named, for example, Vintage, Year, Jaargang or Millésime for the vintage; Size, Volume, Inhoud or Format for the bottle size; and Producer, Producent, Domaine or Winery for the producer.
This step is where most reading mistakes happen, and it is exactly what the spot check is for.
Glassware and accessories
Products that are not wine are sorted into Glassware, Decanters and carafes and Other (openers, corkscrews, gift boxes, packaging, coolers, ice buckets). A title that names a decanter or a carafe counts as a decanter, even when it also says glass. The report counts these items, but Vinius does not publish them: your catalogue in Vinius carries wine only. More in Bringing your catalogue into Vinius.
Choose where Vinius finds the vintage, size and producer
Owners and admins only. Use this when your feed keeps the vintage, the size or the producer under an attribute with a name Vinius does not recognise. It works after the first check.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Click Edit on the integration. On an integration Vinius has enabled, click Pause first: Edit shows while it is paused.
- Under Where the feed keeps the vintage, size and producer, pick the attribute in Vintage, Bottle size or Producer.
- Click Save, then Run integrity check.
In the app
Not in the app: use the web app.
Each list shows the attributes the latest check found, with a few of their values, and how many products carry the one in use. The first option, Automatic, uses an attribute with a usual name, else the product name. On a vintage, size or producer finding in the report, Pick the attribute takes you to the same place.
Saving a change sends an enabled integration back to Draft: run the check again and submit it for review. Your wines stay listed as they were in the meantime.
The two reading rules
- A sparkling or fortified wine without a year is non-vintage is off by default. A Champagne without a year is non-vintage either way. Turn the rule on only when every Cava, Crémant, port or sherry in your feed without a year really is non-vintage. The rule never touches a still wine: a red or white without a year is left out as Vintage unclear, which is better than a wrong vintage.
- A wine without a bottle size is a 75 cl bottle is on by default. Turn it off if you would rather have wines without a size left out (No bottle size) than listed as 75 cl.
You set both rules in the form you get with Connect, or later with Edit.
Prices in your feed
Vinius reads the price in your feed as your list price: your regular price for the wine, whatever you call it (trade, shop or catalogue price). What a business pays less than that is its discount, which you set per customer in the portal. Arrange the feed's pricelist so that it carries that list price.
Vinius asks one thing about it, under Prices in this feed: whether the prices include VAT.
- List prices incl. VAT: Vinius takes the VAT off at the rate in VAT rate to take off (%), a number from 0 to 30. It fills in the standard rate on wine in your country; change it if your prices carry another rate. Check in Odoo whether your shop shows prices with VAT before you choose.
- List prices excl. VAT: Vinius uses the price as it stands.
- No prices (availability only): only for a feed whose prices you cannot use. Venues see your wines and their availability, and get your prices per order.
Only the regular price counts. A promotional price in the feed is ignored, because a promotion is not your list price. A price below €1 or above €5,000 a bottle excl. VAT is treated as a mistake: the wine is published without a price.
Odoo only lets a feed use a pricelist that visitors can select on your website, so treat the feed's prices as public. Put your public list price in the feed and give businesses their price through their discount.
Vinius records every price change with its date. If you later switch to No prices (availability only), your wines keep the last list price Vinius recorded. To remove published prices, contact Vinius.
Findings an Odoo feed gets most often
The integrity check report lists what it found. These are the findings an Odoo feed gets most often:
| Finding | Fix in Odoo |
|---|---|
| Vintage unclear | Add the year to the product name, or as a variant attribute named Vintage. For a non-vintage wine, write NV in the name |
| Two years in one product name | Keep one year in the name, or set the vintage as an attribute, which wins over the name |
| No bottle size or 75 cl assumed | Add the size to the name (75cl, 1,5 L, magnum) or as an attribute named Size |
| Product code appears twice | Give every variant its own Internal Reference |
| No producer | Put the producer in the product name, or add an attribute named Producer |
| Not wine, on a real wine, or a wine counted under Other items | Take words such as glass, gift box or tasting out of its name, and check its categories |
| At least 50% of the drinks are wine fails | The feed holds more spirits and beer than wine: edit the Vinius feed under Manage feeds and leave those categories out |
Every check and every finding, with its fix: Reading your integrity check report.
When Vinius cannot read your feed
When a check or a sync cannot read the feed, there is no report. The Integrations tab shows what happened, the steps under How to fix it and the Technical details, with a link to the matching section below. Once Vinius has enabled the integration, the owners and admins of your organisation also get an email with the same steps.
Where a step says to paste the link again: on an integration Vinius has enabled, click Update link. When only the access token changed, the integration stays scheduled. On an integration that is paused or not enabled yet, click Edit. Then click Run integrity check to try the link.
The link leads to another website
The shop sends the feed link on to an address that is not its own website. Vinius does not follow it there, because the link carries your access token. Open the link in a private browser window and note where it ends up. In Odoo, check under Website › Configuration › Settings that the website's domain is that address, then copy the link again with Copy URL and paste it.
The link leads to an http:// address
Vinius only reads a feed over https, so nobody can read the access token along the way. Set the website's domain in Odoo to its https:// address, copy the link again and paste it.
The shop asks for a login
The shop sends Vinius to its login page instead of the feed. The feed may not be public, or the link may no longer belong to an active feed. In Odoo, open Manage feeds and check that the feed is active and the website is published. Then copy the link again and paste it.
The shop keeps redirecting
The shop redirects the link again and again and never sends the feed. Open the link in a private browser window: you should see XML that starts with <rss>. If you land on another page, check the website's redirects in Odoo, then copy the link again and paste it.
The shop did not answer in time
Run the check again later: the webshop may have been busy. If it keeps happening, leave categories Vinius does not need out of the feed, so it gets smaller.
The shop's address does not exist
Check the domain name in the link for a typo, and check that the webshop opens in a browser. Copy the link again and paste it.
The shop's server refused the connection
Check that the webshop opens in a browser, then run the check again later. If it keeps failing, ask your web host or Odoo partner whether a firewall blocks automated requests to /gmc.xml.
The shop's certificate is not trusted
The certificate may have expired, or it may not match the domain. Open the webshop in a browser and look for a certificate warning. Ask your web host or Odoo partner to renew or fix it, then run the check again.
Vinius could not reach the shop
Check that the link opens in a private browser window and shows XML, then run the check again later. If it keeps failing, contact Vinius support and send the technical details shown on the Integrations tab.
The shop asked Vinius to log in (401)
The feed or the website may not be public. In Odoo, open Manage feeds and check that the feed is active and the website is published. Then copy the link again and paste it.
Odoo refused the link (403)
The access token in the link may be wrong, or the feed may have been deleted and created again, which gives it a new link. Open the feed under Manage feeds, copy its link again with Copy URL and paste it.
Odoo cannot find the feed (404)
The feed may be switched off, or deleted. Check under Manage feeds that the feed exists and is active, then copy its link again and paste it.
The feed was removed (410)
Create the Vinius feed again under Manage feeds, with your wine categories, then copy its link and paste it.
The shop turned Vinius away (429)
The shop limits automated requests. Ask your web host or Odoo partner to let ViniusCatalogBot read /gmc.xml, then run the check again.
The shop did not recognise the link (400)
Copy the link again with Copy URL, without shortening or changing it, and paste it.
Vinius did not try the link
The link must be the public https:// address of your webshop, exactly as Copy URL gives it. Copy it again and paste it.
The shop answered with an error
Run the check again later: the webshop may have had a temporary problem. If it keeps happening, ask your web host or Odoo partner to look at the server log for /gmc.xml.
The link does not return a product feed
The link returned a page of the webshop, usually a login or error page, instead of the feed. Open the link in a private browser window: you should see XML that starts with <rss>. Then copy the link again with Copy URL and paste it.
The feed file is too large
Leave categories Vinius does not need out of the feed, such as spirits or gift sets. Still too large? Contact Vinius support.
The feed has more than 5,000 products
One integration reads 5,000 products at most. Leave categories Vinius does not need out of the feed, such as spirits, gift sets or accessories. More than 5,000 wines? Contact Vinius support.
The feed has no products
Check that the Vinius feed has your wine categories selected and that those wines are published on the webshop. Then run the check again.
The check stopped before it finished
Run the check again. If it fails twice, contact Vinius support and send the technical details shown on the Integrations tab.
Paste a new feed link
Owners and admins only. You need a new link when Odoo gave the feed a new one, for example after you created the feed again.
On the web
- In Odoo, open Manage feeds and click Copy URL on the Vinius feed.
- In Vinius, in the menu on the left, click Catalogue, then the Integrations tab.
- On a failing integration, click Update link, paste the link into Feed link and click Save link. On an integration that is paused or not enabled yet, click Edit, paste the link and click Save.
- Click Run integrity check to try the link.
In the app
Not in the app: use the web app.
When only the access token changed, a failing integration stays scheduled, and the next sync publishes again. The link itself cannot be changed in Odoo. To get a new one, for example after it was shared by mistake, delete the Vinius feed under Manage feeds, create a new one and paste its link as above.
Change the settings of an enabled feed
Owners and admins only. The settings are the prices, the two reading rules and where the feed keeps the vintage, size and producer.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- Click Pause, then Pause again under Pause this integration?.
- Click Edit, change the settings and click Save.
- Click Run integrity check, then Submit for review.
In the app
Not in the app: use the web app.
The integration goes back to Draft until Vinius reviews and enables it again. Your wines stay listed as they were in the meantime. A new access token for the same feed is not a change: it keeps the integration as it is.
Keeping it up to date
Vinius reads the feed on its schedule, and every sync passes the same checks as the first. Odoo itself refreshes the feed about once a day, so a change you make in Odoo can take up to two days to reach buyers. Vinius can read it sooner on request, but Odoo may still serve the file it built earlier that day.
- Wines and items that leave the feed (unpublished, or moved out of the feed's categories) are no longer listed. Nothing is deleted, and a wine that comes back is listed again.
- A sync that changes much more than usual is held: many wines gone at once, many wine prices changed at once, or one wine price moving sharply. You see This sync is on hold. Vinius checks the report and publishes or discards it; buyers keep seeing the previous state until then. See Every sync is checked again.
- A feed that cannot be read turns the integration to Failing, and you get an email with the reason and the steps to fix it (see When Vinius cannot read your feed above). Your wines stay listed as they were, and the next successful sync makes it Active again.
- Once a product code is live, it stays linked to the same wine. Later syncs change its availability and price, not which wine it is. That is why the spot check comes first. If a code is linked to the wrong wine, contact Vinius.
- To change the schedule, contact Vinius.
Stop or remove the feed
Owners and admins only.
On the web
- In the menu on the left, click Catalogue, then the Integrations tab.
- To stop every sync, click Pause, then Pause again under Pause this integration?. Your wines stay listed as they were at the last sync. To resume, click Ask Vinius to resume: Vinius is told and resumes the syncs.
- Before Vinius enables an integration, Remove deletes it together with its integrity checks: click Remove, then Remove integration.
In the app
Not in the app: use the web app.
Deleting the Vinius feed in Odoo, or switching the feed off, stops Vinius from reading it. The integration then shows Failing, and your wines stay listed as they were.
To take your wines off Vinius altogether, contact Vinius: the portal has no button for that.