Filter the open issue queue and read the exclusion reason.
Identify the affected SKU and product directly in the row.
Open the source product to investigate the missing image.
Review feed and local-inventory settings / Actual Odoo screenEnlarge screenshot ↗
02 / Commerce administrator
Review feed and local-inventory settings
Review image, price and stock eligibility before generation.
Keep the primary catalog separate from local-inventory data.
Inspect current output, last-run status and retained snapshots.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Turn a missing listing into a repairable product issue.
The business problem
Generating a file is only part of publishing a useful catalog. Missing images, invalid rows, and unclear failures need a work queue that the merchandising team can act on.
What we changed
Product-level issue queues identify excluded items and link to the source data that needs repair.
What the team can do now
The team can identify why a product was excluded, fix the source product, and inspect the next generation result.
Read the actual screen
An export warning becomes a product task.
The QA queue contains open Missing Image issues, with internal references, product names and an Open Product action in the same row.
Issue
Missing Image
State
Open
Repair path
Open Product
Output types
Primary + local inventory
What the screen shows
The feed configuration exposes image eligibility separately from price and stock eligibility. The issue is tied to a source product.
What the team does next
Inspect and repair the source image, then review issue resolution and the next generated output. No repair or generation was performed for these captures.
What the next team receives
Merchandising receives a specific product to fix, while the integration retains output and run context.
How the work moves
Follow the work from one decision to the next.
01
Generate from source data
Select the appropriate website products and calculate prices through Odoo's pricelist engine.
02
Make the issue actionable
Surface excluded products and missing-image issues, with a direct path to the source product.
03
Repair and regenerate
Fix the product and inspect the next run. Keep primary catalog and local-inventory outputs distinct.
Build notes and background
Data integrationEcommerce UX
Make the exceptions part of the workflow.
Product identity stays consistent
Local-inventory rows use the primary feed’s product IDs; they are a separate data source, not another product catalog.
A source repair is traceable
Missing-image issues link to the source product and resolve when its main image becomes available.
Output history matters
Generation and retained snapshots are visible separately from the source-data repair.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
A custom Pro-A-Motors feed and QA workflow built around Odoo product, website, inventory and pricelist data. Google Merchant Center remains the external publishing service.
