Feeds
Check the product feed for Google Shopping and Meta, fix issues, map Google categories and download the feed files.
Feeds checks your products against the rules of Google Shopping and Meta (Facebook/Instagram) before the platforms complain. It shows which products have errors, what exactly is wrong and how to fix it. You can also load the platforms' own messages, assign Google product categories and download the feed as a file.
Where to find it
Open Shop and customers > Feeds. The area has six tabs:
| Tab | What it shows |
|---|---|
| Overview | Key figures of the last scan, the most common issues and the scan history |
| Issues | All products with issues, with filters and search |
| Platform messages | The real messages from Google and Meta, and the API access |
| Google category | Mapping of your shop categories to Google product categories |
| AI readiness | How well AI search and assistants can understand your products |
| Rules | All checks, their on/off switches and the shop settings |
What you need
- A connected shop. See Onboarding.
- The right permissions. They are listed under the group Feeds. See Access.
| Permission | Needed for |
|---|---|
| View feeds | Opening the area and reading all tabs |
| Run scans, import reports, decide on suggestions | Scan now, importing reports, fetching messages, accepting or rejecting category suggestions. Writes nothing to the shop. |
| Write Google categories to the shop | Preview, Write to shop and the category of a single product |
| Rules and settings | Switching rules on and off, the shop settings, the API access, Create fields in shop |
| Download feed files | The buttons Google XML and Meta XML |
- For writing Google categories the shop must not be read-only. A read-only shop refuses changes.
- No AI key is needed. The scan and AI readiness work with fixed rules, not with an AI service.
How do I run a feed check?
- Open Shop and customers > Feeds.
- Click Scan now. All products are checked again against the Google and Meta rules. Nothing is written to the shop.
- Wait until the page reloads. A large shop can take a few minutes. You can follow the scan under Jobs.
After the first scan the check runs every night on its own. The table Scan history shows each run with its trigger (manual or nightly).
Note: If the banner Only some products were scanned appears, the shop did not deliver all products in time. The next scan continues where this one stopped.
How do I read the overview?
The tiles at the top are links. A click opens the matching list.
- Google: products with errors and Meta: products with errors: the platform rejects these products. Fix them first.
- Google: products with warnings and Meta: products with warnings: the products are accepted but shown less often.
- Google: no issues and Meta: no issues: share of products without any issue.
- Google category present: how many products have a Google category ID.
- AI readiness (average): average score from 0 to 100.
- After you loaded platform messages, more tiles appear, for example Flagged by Google (products) and Flagged by Google only.
Below that, Most common issues on Google and Most common issues on Meta list the checks that hit the most products. Click the product count to see the affected products.
How do I find and fix issues?
- Open the tab Issues.
- Narrow the list: click the tiles Error, Warning or Tip, or type into Search product, number or brand.
- Click the arrow at the start of a row to see the issues right in the list. Click the row or Open product for the full view.
- On the product page read Issues and suggestions. Each issue shows the message, the affected item number, the current value and a suggestion for the fix.
- Fix the data in the shop or in the matching plinth area, for example Products, Images or Properties.
- Run Scan now again. Fixed issues disappear from the list.
The three levels mean:
| Level | Meaning |
|---|---|
| Error | The platform rejects the product. Fix first. |
| Warning | The product is accepted but shown less often. |
| Tip | Recommendation. Improves reach and clicks. |
Note: Feeds does not change product texts, images or prices itself. The only thing it writes to the shop is the Google product category.
Hand an issue over as a task
If you cannot fix an issue yourself, click Create task in Quality on the product page. The task form opens with the product number. Nothing is created until you save it. See Quality.
How do I fix many findings at once?
Many issues have one common cause. Work from the cause, not product by product.
- On the Overview, look at Most common issues on Google and Most common issues on Meta.
- Click the product count next to an issue. The tab Issues opens, filtered to this one check.
- Fix the cause for the whole group. For missing Google categories use the tab Google category: one mapping covers all products of a shop category. For data in the shop use Bulk editing.
- On the tab Platform messages you can use Create tasks (flagged by platform only) or Create tasks (all flagged products) to hand over all flagged products as tasks.
- Run Scan now and check the figures again.
How do I load the messages from Google and Meta?
The tab Platform messages shows what the platforms really complain about and compares it with the plinth checks. There are two ways.
Upload a report
- Export the diagnostics as a CSV file in Google Merchant Center or in Meta's catalog diagnostics.
- Open the tab Platform messages and go to the card Google Shopping or Meta (Facebook/Instagram).
- Choose the file and click Import report.
Fetch directly
- Set up the API access once (see the next section).
- Click Fetch via API on the card of the platform.
After that the card shows a table of messages. The tiles mean:
- Products the platform flags: according to the last report.
- Reported by platform only: the platform complains, no plinth check does.
- Reported by rules only: plinth finds an issue the platform did not report. Only reliable with a complete report.
- Unmatched IDs: items from the report that are not (or no longer) in the shop.
Click a message to see the products with this problem. If the comparison is missing, run a scan first.
How do I connect Google Merchant Center or Meta?
You need the permission Rules and settings and the access data from the platform. Ask your administrator for them if you do not have them.
- Open the tab Platform messages.
- On the card of the platform, open API access.
- For Google: choose the Sign-in type, Service account (JSON key) or OAuth (client and refresh token). Enter the Merchant Center account ID and the matching keys.
- For Meta: enter the Catalog ID and the System user token. Feed ID (empty = all feeds) is optional.
- Optional: fill in Automatic fetch (cron, empty = off) to fetch the messages on a schedule.
- Click Save, then Test connection.
The label next to API access changes from not set up to set up. Keys are stored encrypted and never shown again. A key field you leave empty keeps its stored value. Delete keys removes the stored keys; click it a second time to confirm.
The same place is listed on the Setup page as Connect Merchant Center and feeds.
How do I assign Google product categories?
Without a Google product category Google classifies a product itself. plinth suggests a Google category for each shop category. You decide, then write the result to the shop.
- Open the tab Google category. Each row is one shop category.
- Click the tile To review. These rows have no confident suggestion and need your choice.
- Click a row or Assign category. Pick one of the suggestions or use Search Google category (name or ID, at least two characters). A click on a match assigns it.
- For rows with a suggestion use Accept, Choose another or Reject.
- Click Preview. You see what would be written. Nothing changes.
- Click Write to shop. All confident suggestions and all accepted mappings are written. You need the permission Write Google categories to the shop.
The statuses:
| Status | Meaning |
|---|---|
| To review | No confident suggestion. You need to choose. |
| Suggested (high confidence) | Is written with the next write unless you change it. |
| Accepted | Confirmed by a person, not in the shop yet. |
| Rejected | Nothing is written for this shop category. |
| Written | The Google category is in the shop. |
| Present | The category already had a Google ID in the shop. It stays as it is. |
Note: Your decisions are only noted in plinth. The shop changes only with Write to shop.
Undo a write
After writing, the result window lists the changes and offers Undo. You can also undo the job later under Jobs.
If your role needs approval
You then see Submitted for approval. Nothing is changed until a team lead approves. The write runs after the approval. See Approvals.
Set a different category for one product
- Open the product from the tab Issues.
- In the card Google product category use Search Google category and click a match.
- Click Preview to check, then Set for this product.
The choice applies to this product only and wins over the shop category. Remove override makes the shop category apply again.
Make the fields visible in the shop
Create fields in shop creates the custom fields for the Google category once, so they can be seen and edited in the shop admin. It needs the permission Rules and settings and a shop that is not read-only.
How do I check the AI readiness?
- Open the tab AI readiness.
- Use the tiles Low, Medium and Good to filter the product list by score.
- Most common gaps shows what is missing most often and how to fix it.
- Crawlers and sitemap shows which search and AI crawlers are allowed or blocked by the shop.
- Open a product. The card AI readiness lists its score and the Missing information.
How do I switch rules on or off and change settings?
- Open the tab Rules. The table lists every check with platform, field, severity and message.
- Clear the box in the column Active to switch a rule off. It is no longer reported from the next scan on.
- For thresholds, field mapping and exceptions open Settings for this shop (advanced), change the values and click Save.
Both need the permission Rules and settings.
Warning: The advanced settings are a technical text block. A wrong value changes the results for the whole shop. Change them only if you know the format, or ask your administrator.
How do I download the feed files?
- Open the tab Overview.
- Click Google XML or Meta XML. The current feed is built from the shop and downloaded as a file.
You need the permission Download feed files. Every download is recorded in the Audit log.
Common errors and fixes
| Message | Cause | Fix |
|---|---|---|
| Only some products were scanned | The shop did not deliver all products in time. | Run Scan now again. The scan continues where it stopped. |
| A message starting with "The feed was not created" | Not all products could be read, so no incomplete file is handed out. | Download again a few minutes later. |
| The same task is already running. | A scan or fetch is still in progress. | Wait until it has finished. See Jobs. |
| You do not have the permission for this. | A permission is missing, or the shop is read-only. | Ask your administrator. See Access. |
| Nothing to write. | There are no confident or accepted mappings left. | Accept or choose categories first. |
| Please search for a Google category and click it first. | No match was chosen for the product. | Search, click a match, then set it. |
| The Google category is turned off in Settings. | The feature is switched off for this shop. | Switch it on in the shop settings on the tab Rules. |
| The fields can only be created in the real shop. | The current shop has no real shop connection, for example a demo shop. | Use the function in a connected shop. |
| The file has no data rows | The uploaded report is empty or is not the diagnostics export. | Export the report again and upload the CSV file. |
| A message about a missing column for the problem or the item ID | The file is not a diagnostics report of the platform. | Upload the unchanged export from the platform. |
| The API connection is not set up. Please import the report as CSV. | No API access is stored for this platform. | Set up API access or upload the report. |
| Sign-in rejected. The key is invalid or has expired. | The stored key is wrong or expired. | Enter a new key under API access and test again. |
| Access denied. A role or permission is missing. | The account at the platform may not read the catalog. | Have the access rights at Google or Meta corrected. |
| The platform's rate limit was reached. Try again later. | Too many requests in a short time. | Wait and fetch again later. |
| Check the input: IDs are numbers, and the cron expression and keys must be valid. | A field of the API access has a wrong format. | Correct the IDs, the schedule or the key. |
| Keys can't be stored because the server master key is missing. | The server is not prepared for storing keys. | Ask your administrator. |
| The JSON is not valid: | The advanced settings contain a typing error. | Correct the text or reload the page to discard it. |
| Invalid settings (check regular expressions, platforms, cron or the names of the custom fields). | A value in the advanced settings is not allowed. | Correct the value named in the message. |