A feed plugin sits between your store’s actual product data and whatever platform you’re submitting to, and most of the recurring feed problems people bring to us trace back to that plugin being mapped incorrectly — a field pointing at the wrong attribute, a filter excluding products it shouldn’t, a schedule that never actually runs.
Check when the feed was actually last generated, not just its settings
Most feed plugins show a “last generated” timestamp. If that’s stale — days or weeks old — the plugin’s mapping and filters may look perfectly correct while the feed itself simply isn’t refreshing, which is a different, often overlooked problem from a mapping error.
Feed plugin configuration & mapping
Your feed plugin's mapping and schedule checked — most recurring feed problems trace back here.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your feed plugin’s settings, or confirmation of which plugin you use
- Confirmation of which platform (or platforms) the feed is meant to be feeding
- Any specific products or fields you already suspect are mapped incorrectly
This or something else?
| Your feed plugin’s mapping, filters, or schedule need reviewing or fixing | This fix covers it |
| You don’t have a feed plugin yet and need one set up from scratch | A related but more involved initial setup |
| The plugin is generating correctly but Google or Meta still rejects products | Product feed disapproval diagnosis & fix, the platform-side version |
| You want feed rules for cosmetic transformation, separate from plugin configuration | Feed rules & supplemental feed setup, a Merchant Center-side approach |
What we do
- Review current plugin configuration, field mapping, and filters
- Check when the feed last actually generated and refresh if stale
- Correct any mapping pointing at the wrong product attribute
- Fix filters incorrectly excluding products that should be included
- Confirm the generation schedule is active and appropriate for your catalogue size
- Verify the resulting feed against the target platform’s requirements
What is included
- Feed plugin mapping and filters reviewed and corrected
- A confirmed, working generation schedule
- Verification against your target platform’s actual requirements
- A written note on what was wrong and the corrected configuration
Not included
- Setting up a feed plugin from scratch, if none currently exists — a related, separate task
- Platform-side disapprovals unrelated to feed generation itself
- Ongoing configuration as your catalogue or platform requirements change
- Multiple platforms’ worth of setup beyond what’s specified
Questions about this fix
How would I know if my feed plugin isn't actually updating?
Most plugins show a last-generated timestamp somewhere in their settings — a stale one, even with correct-looking configuration, is the clearest sign the schedule itself isn't running.
Could a mapping error explain only some products being wrong, not all?
Yes, that's common — a mapping issue affecting a specific attribute (like a custom field) only shows up on products that actually use that attribute, leaving others unaffected.
Do I need a different feed plugin, or can this one be fixed?
Usually the existing plugin can be correctly configured — we'd only recommend switching if the plugin genuinely can't support what your setup requires.
Will this fix work for whichever platform I'm feeding into?
Yes, this is about the plugin's own configuration and mapping, which applies regardless of whether the destination is Google, Meta, Pinterest, or Microsoft.
How often should the feed actually regenerate?
It depends on how often your product data changes — a catalogue with frequent price or stock changes needs a much more frequent schedule than one that rarely changes.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.