Enterprise DNA

Instead of DataFeedWatch

Stop renting DataFeedWatch. Own your product feed system.

We build your version around your catalogues and channel requirements, bring your DataFeedWatch product records across and run it for you. Start with the feeds and checks your team uses every week.

DataFeedWatch lists Agency at US$239 a month and managed service from US$750 a month as an add-on. Enterprise is quoted separately.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the whole bill

The catalogue is yours. The feed service is the recurring bill.

Compare your complete DataFeedWatch scope, including services, with the work you want to own. Its Agency plan is US$2,868 over twelve monthly payments, before add-ons. The free base below prepares local feed files; your managed version can include the connections and delivery you need.

storage

Catalogue capacity

Subscription allowances depend on the size of your catalogue. Your version holds the product records and the source values behind each one.

view_module

Feed allowances

Plans include different feed allowances. Keep each destination, its owner and its rules together in your own system.

sync

Scheduled source updates

DataFeedWatch provides scheduled updates. Agree the source connections and update frequency for your version before switching.

rule

Mapping and rules

Column mapping and channel rules need maintaining as your catalogue changes. Keep that work and its review history with your business.

support_agent

Specialist support

Managed service starts at US$750 a month. Compare the service scope, correction workload and ongoing ownership alongside the software plan.

fact_check

Feed review

Missing titles, broken product details and contradictory stock still need decisions. Give each correction an owner and a due date.

What your version does

Make each feed a record you can explain

Catalogue

Keep the source behind every product

Bring in your catalogue and keep shops separate.

  • check Import the full source catalogue from a downloaded CSV
  • check Keep New Zealand and Australian prices in their own currencies
  • check Retain the original source columns with each product
  • check Read the before and after values when an import changes a record

Rules

Explain what each channel will receive

Apply ordered rules and read why an item was held back.

  • check Set a channel owner and output format
  • check Label products from your own category rules
  • check Review every excluded product and the rule that excluded it
  • check Compare additions, changes and removals with the previous reviewed feed

Checks

Catch the records that block release

Find missing details and conflicts before a feed file is prepared for delivery.

  • check Flag missing titles, descriptions and image addresses
  • check Check identifier format and conflicting stock values
  • check Apply a freshness policy for each source catalogue
  • check Assign overdue corrections to a named owner

Review

Keep proof of the review with the feed

Save the prepared records and review them before creating the output file.

  • check Record who prepared and reviewed each feed
  • check Require a new review when source records or rules change
  • check Produce a catalogue review and correction list in your brand
  • check Draft the weekly review from source health, stock and open work

Make it yours

Design your own DataFeedWatch replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from DataFeedWatch. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your DataFeedWatch replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your DataFeedWatch data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Product Feeds for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Product Feeds for Claude Code

Connected to your own database

Which products need correcting before the next feed?

Koru Shopping

Sku
BOTTLE-1
Rule
STOCK_CONFLICT
Severity
error
Message
Zero quantity contradicts in-stock availability

Koru Shopping

Sku
MAT-1
Rule
TITLE
Severity
error
Message
Title is missing or exceeds 150 characters

Koru Shopping

Sku
MAT-1
Rule
IMAGE
Severity
error
Message
Image link must be an absolute HTTP or HTTPS address

Ask it anything

Ten questions your version answers today

These questions run against the fictional demo records. Build your own checks around the decisions your team makes.

chat_bubble Which products have no stock but say they are available?
chat_bubble Which shop has the oldest source observations?
chat_bubble Why was a product excluded from a channel?
chat_bubble Which records block the next feed file?
chat_bubble Which identifiers need checking?
chat_bubble Which catalogue correction is overdue?
chat_bubble What changed since the previous reviewed feed?
chat_bubble Who reviewed each saved feed run?
chat_bubble What source values changed during an import?
chat_bubble What did the original source say about this product?

Switching

How to switch from DataFeedWatch

The move involves exporting your catalogue, mapping its fields and rules, checking the imported records, then comparing the replacement with your current setup before you switch.

  1. 1

    Download your source products

    Use DataFeedWatch’s documented full-source CSV download from the store options to export your product records. Headings follow your source shop, so keep a sample available for mapping. The product export does not include your DataFeedWatch rule definitions or account connections. List those separately so you can rebuild and test the rules and confirm how each connection will be handled.

  2. 2

    Map and preview the import

    Load the CSV into the replacement and map your source headings to its product fields. Start with the import preview or test run, if available, before saving business records. Reconcile the preview’s product counts and currencies against your source. Use the real source observation time. Missing rows do not delete existing products, so check how the replacement handles any products you expected to remove.

  3. 3

    Review flagged records and rules

    Check the import results for duplicate identifiers, malformed values and changes to source values. Then review the product checks, exclusions and records that block a feed. Confirm that channel rules have been rebuilt and tested, since they do not come across in the product export. Your team still needs to check store parity, images, shipping, tax and category requirements before release.

  4. 4

    Run both systems side by side

    Keep DataFeedWatch running while you prepare feeds in the replacement for a short period. Compare product counts and currencies, included and excluded products, rule outcomes and the records that block release. Review the output files and check them against the live store and each channel’s requirements. The free base creates local files, so include any live connections and hosted delivery your business uses in the comparison.

  5. 5

    Switch off DataFeedWatch

    Switch off DataFeedWatch only after the side-by-side review shows that the replacement covers the work you need. Confirm the plan for live connections, delivery and ongoing operation, since these may need to be scoped separately from the free base. Keep the source files and database backed up, and make sure the people responsible for product and channel reviews know the new process.

construction

Where the real effort goes

The main work is usually mapping your shop’s fields, rebuilding your channel rules and deciding how much history to bring across. The product CSV brings source records, not rule definitions or account connections. Check counts and currencies, then test the rebuilt rules and review process. If Enterprise DNA installs and runs your version, they handle this mapping and setup work as part of the agreed scope.

Not ready for a call?

Get your DataFeedWatch switch plan by email

We will send you the step-by-step plan for moving your business off DataFeedWatch, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm run demo and npm test
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and inspect the fictional catalogues
  3. 3 Download your DataFeedWatch source CSV, map its headings and preview the import
  4. 4 Rebuild your channel rules, review an output file and arrange delivery separately
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your source headings, channel fields and catalogue rules
  • check Your DataFeedWatch records brought across and reconciled
  • check The source connections, destination delivery and screens your team needs
  • check A different technical foundation when your business requires it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and recovery checks
  • check Source updates and feed delivery built around your agreed channels
  • check Catalogue corrections and weekly reviews prepared for your team
  • check Run through Omni by Enterprise DNA, beside the rest of your business
Book a product feed review

Questions

Instead of DataFeedWatch, answered

Is this the whole DataFeedWatch service? expand_more

The free version handles catalogue records, channel rules, supported feed checks, review history and local output files. We scope the live connections, hosted delivery, additional channel fields and ongoing operation your business needs as part of your version. Compare the complete workflow before cancelling your existing service.

Can we bring our DataFeedWatch products across? expand_more

Yes. DataFeedWatch documents a full-source CSV download from the store options. Source headings vary by shop, so we map a sample, do a test run and reconcile the product counts and currencies. A product export does not carry your rule definitions or account connections. We rebuild and test those separately.

Will every product be accepted by Google? expand_more

Acceptance stays with the destination. The free version checks supported product details and stops a release with errors. Your team still checks the live store, images, shipping, tax and category requirements. Apparel and products awaiting stock require additional fields in your version before release.

What happens when prices or rules change after a review? expand_more

The saved feed keeps the records it was prepared from. A later source or rule change requires a new review before creating the output file. Old stock observations also block release. The reviewer sees what changed and which products were excluded.

How does Enterprise DNA charge? expand_more

There is one setup fee, then a retainer for the ongoing work and operation you agree with Sam. Bring your current DataFeedWatch plan, service scope and a sample catalogue. We work through what your version needs before agreeing the scope.

Bring your DataFeedWatch bill and a sample catalogue

Book 30 minutes with Sam. Walk through your channels, recurring corrections and service scope, then decide what your own version needs to do.

Book 30 minutes with Sam Get the free version

Product Feeds for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DataFeedWatch?

Get your version built