Title & ID rail
title → id → item_group_id mapped per channel rules.
- GTIN / MPN checks
- Variant grouping
E-commerce solutions · Feed pipeline
Liberty Weblab
Shopping feed management that improves product match quality
Product data moves Source → Map → Validate → Sync → Channels. We build the rails so listings and ads reflect the catalog you actually sell - not yesterday's export.
Channel mapping nodes
One catalog truth - field nodes wired to each destination
Map identifiers, variants, and labels once, then route them down channel-specific rails.
Validation meters
Catch broken rows before they leave the rail
Pre-sync gates score completeness and surface the error types that kill coverage.
Required fields
94%
Identifier coverage
88%
Price / stock fidelity
97%
Image / URL match
76%
Error types we gate
- Missing ID GTIN, MPN, or brand gaps
- Drift Price or availability vs landing page
- Malformed Bad URLs, empty titles, broken variants
- Policy risk Restricted claims or weak product pages
- Stale sync Rows older than your inventory pace
Multi-channel split
Same source - different rails for each destination
Rail A · Shopping destinations
Google-ready product feeds
Attributes shaped for Shopping destinations - identifiers, shipping, and custom labels that support bidding and reporting later.
- Primary + supplemental field maps
- Coverage control by SKU segment
Rail B · Channel & marketplace feeds
Destination-specific payloads
When other channels need different schemas, we fork the map - not force one CSV into every endpoint and hope it sticks.
- Per-channel include / exclude rules
- Variant and taxonomy adaptations
Sync cadence
A schedule matched to how fast your inventory moves
Rails only help if the sync clock matches price and stock reality.
-
01
Hourly / daily
Source pull
Catalog truth ingested from store, ERP, or feed source on the agreed window.
-
02
Per sync
Map & transform
Field nodes apply channel rules, labels, and include/exclude logic.
-
03
Pre-publish
Validate gate
Meters run - bad rows quarantine before publish, not after shoppers notice.
-
04
Scheduled
Channel push
Approved payloads sync to each destination rail with a change trail.
-
05
Ongoing
Health check
Coverage, error rates, and stale SKUs reviewed so cadence can tighten when needed.
Before / after
Broken sync vs clean rails
Broken sync
- Manual CSV uploads when someone remembers
- Wrong fields mapped - or blank - per channel
- Errors found after ads or listings fail
- Stock and price drift for days
- No trail of what changed when
Clean rails
- Scheduled Source → Channels pipeline
- Mapping nodes reused across destinations
- Validation meters gate every publish
- Cadence matched to inventory volatility
- Health report with coverage and next fixes
Feed ops in view
From mapping workspace to channels in sync
See the rails your catalog rides - map, validate, and push with channel-ready truth.
03
Channels in sync
Same catalog truth across destinations
01
Source & pull
Catalog enters the rail
02
Field mapping
Nodes that match each channel
04
Inventory cadence
Stock-aware pushes on schedule
Why Liberty Weblab
Operators get pipelines - not one-off feed dumps
Rail-first design
Source → map → validate → sync → channels, with clear handoffs.
Multi-destination fluent
Feeds shaped for how each channel consumes data - not a single forced format.
Maintainable cadence
Rules and schedules your team can keep running after launch.
FAQ
Shopping feed management questions
What is shopping feed management?
Shopping feed management keeps product data flowing from your catalog to advertising and shopping channels - with clean mapping, validation, and sync schedules so listings stay accurate.
How is this different from Merchant Center management?
Merchant Center management focuses on Google account health and approvals. Shopping feed management covers the broader pipeline - source data, mapping, validation, and publishing to one or more destinations.
Which channels can you support?
Google Shopping feeds are common, and we also support channel-specific product feeds when your stack and catalog allow clean mapping to each destination.
How often should product feeds sync?
Cadence depends on inventory volatility. Fast-moving catalogs often need daily or more frequent syncs; slower catalogs can run on a tighter scheduled window as long as price and stock stay truthful.
Ready for sync rails that keep every channel truthful?
Tell us your destinations - we'll map validation gates and a cadence that fits.