Why your Glovo menu prices differ from the ones you set
Restaurant operators on Glovo face the most expensive price parity rule published by any of these platforms. Glovo’s partner terms bind the partner to what they call the “Parity Model”, warranting that products “will not be offered to GLOVO users at higher prices than those offered by the PARTNER on its own platform”, and add that on breach “GLOVO shall be entitled to charge the PARTNER an additional 10% based on the total amount of gross sales”. Separately, Glovo’s catalog feed ignores bad price lines rather than rejecting them.
What does Glovo’s Parity Model cost if you get a price wrong?
Glovo states the obligation and the sanction in one clause. It begins by confirming that “PARTNER is solely responsible for setting the prices of its products”, then warrants that products sold through the app “will not be offered to GLOVO users at higher prices than those offered by the PARTNER on its own platform, if applicable (hereinafter referred to as the “Parity Model”)”. The consequence is quantified: “In the event of a breach of this obligation, GLOVO shall be entitled to charge the PARTNER an additional 10% based on the total amount of gross sales of products and/or services obtained by the PARTNER from the use of the GLOVO APP during the period of breach” (glovoapp.com partner terms).
Two features of that wording matter operationally. The charge is calculated on gross sales for the whole period of breach, not on the margin from the mispriced items, so a single stale item can carry a cost far larger than the item itself earns. And because breach is defined against the partner’s own platform, a price rise made on the brand’s own ordering site without a matching update on Glovo creates the breach, not a Glovo error.
Who is responsible when a Glovo listing and the restaurant disagree?
Glovo assigns that explicitly, and it is broader than pricing. The terms state that “Any discrepancy between the description appearing on the APP and the product and/or service actually offered at the PARTNER’s establishment (such as, for example but without limitation, a difference between the price stated on the APP and the price offered in store) shall be the PARTNER’s responsibility, and the latter must therefore bear any additional cost that may arise therefrom” (glovoapp.com partner terms).
The clause names a price difference as its worked example, which tells you what the drafters had in mind. Combined with the Parity Model it produces a clear position: Glovo does not undertake to keep your prices right, it undertakes to charge you when they are wrong. That makes the practical question for a Glovo operator not whose fault a mismatch is but how quickly they find one, since exposure accrues for as long as the breach lasts.
Why is the price not updating for a Glovo product?
Glovo publishes that exact question and answers it with a list of failure modes, all of which are silent. Its catalog troubleshooting names the “Common causes: SKU not in catalog”, and “Price = 0 or < sales buffer”. The feed documentation goes further, stating that “If you send price 0 or negative – the line will be ignored”, that when an “SKU does not exist in Catalog… the line will be ignored and you will see “Missing SKU” error”, and that “Duplicate SKUs will result in both lines being ignored” (qcommerce.developer.glovoapp.com).
The word that recurs is ignored, not rejected. A file containing one duplicated SKU is accepted, processed, and quietly drops both copies of that item, so the update succeeds while the item keeps its old price. Duplicate rows are exactly what a merge between two source systems produces, which means the most common way a chain builds a price file is also the way it loses items from that file without being told.
How can a Glovo price file fail because of its name?
Because the vendor is identified by the filename, and Glovo’s own parser is strict about it. The documentation specifies “<prefix>_vendorID.csv for single vendor updates” and “<prefix>.csv for multivendor updates”, and warns that it is “incredibly important to name your file properly, otherwise the file synchronisation will not work”. A separate note adds the trap: “Do not use “_” as part of the prefix as it will stop the file from reading the “vendors” column” (qcommerce.developer.glovoapp.com).
Glovo also documents what happens with a misnamed file, distinguishing two outcomes: “qa_v4ft.csv → system will not read the vendor column in the file”, while a file dropped in the wrong place fares differently, since “Incorrect Folder in glovo SFTP Server was used to drop the file- in this case the file will be rejected”. A rejected file is recoverable because someone notices. A file whose vendor column was not read is the dangerous case, because the prices go somewhere, just not where the operator intended.
Where do you look to see whether a Glovo price actually landed?
In the portal, under the integration plugin rather than in the menu itself. Glovo directs partners that “The Assortment Files can be viewed in Shops Integration Plugin in the Partner Portal”, where “you are able to download the files that have been uploaded and see the errors if any occurred on the item level”, and separately that a “Store Management plugin, accessible through the store’s Partner Portal account” is what “will allow you to check the current product prices” (qcommerce.developer.glovoapp.com).
Glovo’s naming makes even that harder to find than it should be. The same back office is called the “Manager Portal” in Glovo’s own tutorials, described there as “an easy, efficient tool to help you manage your business performance and take action for growth”, the “Vendor or Manager Portal” in the partner terms, and the “Partner Portal” in the integration documentation. An operator following instructions written by three different Glovo teams is being sent to one place under three names.
What else has to be complete before a Glovo listing behaves?
Glovo ties activation to menu completeness in the contract, not just to quality guidance. The terms state that “Partner acknowledges and agrees that in order to be activated on the APP, they must maintain a minimum of 100% of the total photos and descriptions and other required obligations (such as nutritional information) of its products on the menu” (glovoapp.com partner terms). The same document contains a second variant of the clause stating a 70 percent minimum, so the published figure is not consistent within one contract.
For price work this matters because an item missing a required attribute is an item that may not be live, and an item that is not live cannot be checked. Whichever threshold applies, the practical effect is the same: parts of a menu can be absent for reasons unrelated to price while the exposure created by the Parity Model keeps running on everything that is present. Reading the live Glovo storefront branch by branch each day and comparing it against the brand’s own price book, which is what Kitchain (kitchain.co) does, is the only view that shows which items are live and at what price at the same time. Ownership, markets and the wider set of Glovo signals are covered on the Kitchain Glovo page.