Empty fields, filled in from the data already in your catalog.
Preflight finds the fields a channel will reject: missing, not on the channel's list, wrong format. Data Remediation reads the rest of the product, and products like it, works out what the value should be, and hands you a reviewable list of proposed fixes, ordered by how many products each fix unblocks and how safe it is to apply. You review and accept. Your product attributes stay exactly as they are until you do.
Syndic8 works out the missing value from everything else it knows about the product.
A product record is rarely as empty as its blank fields suggest. The form is in the packaging text, the brand is in the style name, the material is in the description. Until now, a person had to read all of that and type the answer, record by record, for weeks. Syndic8's AI reads it instead, across the whole catalog, and shows you where each answer came from.
Found in the product itself
A boot's description says "...sits on a 2-inch stacked heel..." and the Heel Height field is empty. Syndic8 lifts the 2 inches out of the prose and into the structured field. A weed-killer sold in 32 fl. oz. bottles with "mix and apply with a sprayer" on the label has no Item Form; Syndic8 proposes Liquid and says why. Where one product is silent, it looks at the products around it.
Paired to the channel's accepted list
Your marketing color is Midnight. The channel's accepted list has Black. Syndic8 pairs the two automatically, the way a merchandiser would, and remembers the pairing for every template you have for that channel. Champagne Bronze to Yellow is the harder version of the same problem, and it's the kind of judgment only AI or a person can make.
Rewritten the way the channel reads them
A date typed as 10/3/26 where the channel wants 2026-10-03. Search terms separated by commas where Amazon wants spaces. Bullets that run past the 255-character limit. A dimension stored as "12 x 8 x 4" where the channel wants three numeric fields. One decision fixes every product with the same problem.
Eight products, one empty field, five minutes.
A lawn and garden brand runs preflight on 22 products for Amazon. Item Form is required for fertilizer and empty on 8 of them. Here is what Syndic8 does with that.
Syndic8 reads the eight products
Product one: the name says "Weed and Grass Killer Concentrate", the size is "32 fl. oz.", and the directions say to mix according to the label and apply with a tank or hose-end sprayer. Product two: the name says "Liquid Lawn Food", and the description mentions "each 32 fl. oz. translucent bottle." Product three: a "Liquid Plant Food Bundle."
Syndic8 proposes a value and shows its reasoning
Item Form: Liquid, matched to Amazon's accepted value, for all three. Beside each one, the reason in plain language: "Sold in fluid-ounce bottles and mixed before spraying, which indicates a liquid concentrate." The three proposals share one reason, so they appear as one decision, not three.
Syndic8 leaves the rest open, and tells you so
Five products say nothing about their form. Item Form is a factual field, so Syndic8 won't guess. Those five are listed as open with a note that nothing in the data evidenced a value, which is a five-line to-do list for a person instead of a wrong answer sent to Amazon.
You accept, Syndic8 applies, preflight passes
One click accepts the group. The change goes in as a recorded, reversible batch. Preflight runs again and three more products clear Listing Readiness. The same run also found the missing Brand Name on four products at the start of their product names, and proposed a full product title for one grow light that had none, built from its own description.
The next step, once a field is filled, is to optimize it for the channel: a derived product title is a fact; the Amazon version of that title follows Amazon's formula. How Channel Optimization does that.
Biggest impact first. Lowest risk first. The risky fields locked.
Ordered by products unblocked
One empty field across two thousand products is one fix, and Syndic8 puts it at the top. The repair list is sorted by how many products each field is holding back, so a morning's work clears the most listings.
One review for one answer
When four hundred products need the same value for the same reason, you review and approve it once. Open the group to see every record, untick the ones that don't belong, or correct a single value and push it across a selection.
Prices and specs are never guessed
Syndic8 will not propose a price. Its own words on a locked price field: a price is a commercial decision that nothing in your catalog can answer. The same holds for regulated values and for any factual field without evidence. It would rather leave a blank than put a wrong number in front of a retailer.
Data problems and plumbing problems kept apart
Sometimes a field is empty because the export is reading the wrong column, not because the data is missing. Syndic8 says which it is, so you fix the mapping once instead of generating values to paper over it.
What people ask before they turn it on.
Does it change my core product data?
Only if you choose that. A proposed value can land as the channel's value or as the core value, and nothing lands until it's approved. Until then it's a draft beside your data, not a change to it.
Can my team work on it at the same time?
Yes, and everyone's work lands in one shared list. Every proposed fix, from anyone on the team, goes into the same central queue for that channel, so the whole team sees what's been proposed, who approved what, and what's still open. Runs happen in the background and email you when they finish, so nobody sits watching a progress bar.
Does it know that boots on Zappos and boots on Amazon need different things?
Yes, because it works per channel per product type. The required fields, the accepted values and the formats all come from that channel's template for that category, so shaft height is required on one and optional on the other, and the color lists differ.
What if it's wrong?
Every proposal shows its source and its reasoning before you accept it. Every applied change is recorded, with what it wrote, when and by whom, and can be undone.
Can I run it from Claude or ChatGPT?
Yes. Your assistant can run preflight, start the remediation and read the proposals through the MCP server. Approval still happens in Syndic8, by a person with the permission to do it. How the MCP server works.
What does it refuse to do?
Invent a price. Invent a flow rate, an energy rating, a Prop 65 statement or a certification. Fill a factual field it can't evidence. Write anything without approval.
Free data evaluation. Send a product file and name the channel.
We'll run preflight, then show you the repair list: which fields block the most products, what Syndic8 can fill from your own data, and what still needs a person. No commitment, and nothing changes in your data.