A new idea for WooCommerce

Your next feed.
A little more
foresight.

Meet the idea behind WPFeed: a preflight check for your product feeds. See what changed, understand the risks, and make the call before the next update goes out.

In product planning. No plugin download yet.

THE FEED BEFORE THE FEED01 / PREFLIGHT
WPFeed / Feed reviewCONCEPT
STORE → PRODUCT FEED

A change worth catching.

Sample data
Products checked128
Changed12
Needs a look3 ↗
PRODUCT / SKUCHECK
Everyday sneakerSNK-042 · Price changed
Review
$89.00$8.9090% drop
Canvas weekenderBAG-016 · Stock mismatch
Review
Studio desk lampLMP-008 · No change
Clear
A price change. Or a misplaced decimal?Let the merchant decide before the feed updates.
Your store. Your thresholds.The proposed WPFeed approach.
THE DIRECTION

WooCommerce first.

Explain every flag.

Keep the merchant in control.

01 / THE OPPORTUNITY

Sending products is easy.
Knowing what you’re sending?

Exporters already connect stores to shopping channels. We’re exploring the moment just before that handoff: the changed price, the missing variant, the product that quietly disappeared.

WPFeed’s proposed focus is a review layer for WooCommerce feeds, with clear evidence for each decision. Start with an existing feed. See the difference. Decide what happens next.

See the proposed scope
02 / TRY THE THINKING

Less guesswork.
One product at a time.

Click through three example checks.
This is an interactive concept, not a live store scan.

PRICE CHANGE / SAMPLESKU: SNK-042

A decimal shouldn’t
make the decision.

Previous feed$89.00
Next feed$8.90
Why this would be flagged

A 90% price drop exceeds a merchant-defined 30% review threshold. The intended workflow asks for approval rather than silently passing it through.

Proposed check · illustrative values · no feed has been changed

03 / THE PRODUCT THESIS

Build around the decision.
Not just the export.

The workflow we want to explore with store owners and the agencies who look after them.

CHANGE INTELLIGENCE

Show the before.
Explain the after.

A field-level comparison of prices, inventory, identifiers and variants. Each flag should link back to the product and the values behind it.

MERCHANT GUARDRAILS

Your business rules.
Visible consequences.

Explore price-drop limits and stock checks first. Later, test margin rules with merchant-supplied cost data and explicit assumptions.

FEED RELEASE WORKFLOW

Review. Approve.
Keep a record.

A proposed approval log and versioned feed snapshots. Start read-only; publishing controls come after the inspection workflow is proven.

These are proposed capabilities. They are not available in a released WPFeed plugin.

04 / BUILD IT IN THE RIGHT ORDER

A focused start.
Room to grow.

First, make feed changes understandable. Then consider taking responsibility for sending them.

Tell us what your store needs
  1. 01
    PROPOSED FIRST RELEASE

    The read-only inspector

    Inspect a supported product feed, compare snapshots, and flag price, availability and variant changes. Prove the checks on real stores.

  2. 02
    NEXT, IF VALIDATED

    Rules & review history

    Merchant thresholds, explainable exclusions, agency review and reports. Validate each exporter integration before promising support.

  3. 03
    LONGER-TERM EXPLORATION

    Controlled feed publishing

    Approved feed versions and publishing safeguards. A restored file would not reverse changes already ingested by a shopping channel.

A FEW GOOD QUESTIONS

Before we
build the feed.

Can I download WPFeed today?

No. This is the product concept and planning site. There is no released WooCommerce plugin, confirmed launch date or price yet. The interactive examples use sample data.

Would it replace my current feed plugin?

The proposed first step is an inspection layer for an existing feed, so you would not need to replace a working exporter just to try it. Exact feed formats and exporter compatibility still need development and testing.

Is this completely new to the market?

Feed validation, rules and diagnostics already exist. Our hypothesis is that a focused WooCommerce workflow combining change review, merchant guardrails and explainable decisions could be useful. We are not claiming to be the only product with these ideas.

Would it guarantee channel approval or better sales?

No. A feed check cannot guarantee platform approval, ad performance or revenue. Shopping channels make their own eligibility decisions, and profitability depends on costs and data beyond a product feed.

Where did the WordPress articles go?

The existing WPFeed publication is now in the blog. Previous article URLs redirect to their new addresses, and the original articles and media are preserved.

FROM THE WPFEED ARCHIVE

Still curious about WordPress.

Explore the blog

Our existing WordPress articles, with their original publication dates.

WPArena.com Case Study

In this case study, we will delve into the world of WPArena, a popular WordPress resource website. We will explore its history, competitors,…

Read article
LET’S MAKE FEEDS MAKE SENSE.

What should your feed
catch before it goes live?

Help shape WPFeed