Product and master data
Product and master data sync keeps the same product consistent across systems: Runtara reads the record from each system, applies the rule you agreed for each field, and sends ambiguous differences to a person before a correction reaches the catalog.
01 / The problem
Why it is still manual.
Your ERP and storefront describe the same product, and they drift apart. A one-way overwrite spreads whichever value is wrong to every channel.
Most fields have an obvious owner. The ones that do not need a person who knows the product.
Scroll sideways to compare all fields.
| Field | ERP source | Catalog | Decision |
|---|---|---|---|
| Material | Stainless steel | Stainless steel | Agrees |
| Length | 42 mm | 40 mm | Review source |
| Pack size | 100 | 100 | Agrees |
Keep both source values with the proposed correction. A person confirms the authoritative value before the catalog is updated.
02 / How it runs
The workflow, step by step.
- Compare
On a schedule or on change, the same product is read from each system and lined up.
- Resolve
Fields with an owner follow the rule. Unclear differences wait for a person, both values shown.
- Update
The validated value is written where it is needed, with what changed and who decided.
The reviewer sees both values and the rule that could not decide, so the fix is made once.
03 / Under control
What stays under control.
Rules per field, not per system
Pick which system owns each field: price from the ERP, descriptions from the catalog team.
Held means unwritten
A difference under review is published nowhere until a person answers.
A record of every correction
Each run keeps the values read, who decided and the write, so a wrong fix can be traced and reversed.
04 / Systems
Systems it connects.
Examples from the supported connections. Other systems are scoped during implementation.
05 / Questions
Common questions.
Which system is the source of truth?
You decide per field. A rule settles the fields with a clear owner; the remaining differences go to a person instead of being overwritten.
What happens to a difference nobody has reviewed yet?
It stays held and unwritten. The run resumes from its last committed step when someone answers, without repeating the reads it already made.
Can we see what changed and why?
Yes. Each run keeps the source values, the decision, and the write in the instance database, and reports let you review differences across many products.
Does it work with Shopify?
Yes. The Shopify connection covers products, variants, prices, metafields, images, tags, inventory, locations, and collections, including bulk product updates.
How is it priced?
Start with a paid pilot of this one process on Cloud. Each process has a one-time implementation fee, quoted from the systems, rules, and exception paths involved, plus the plan subscription. There are no per-task fees or run-count limits. Enterprise includes one agreed process.
Bring us the process.
Show us the systems involved, the records that move between them, and the exceptions your team handles. We will map the steps and scope a first workflow.