Send the right products, the right way, on schedule
Product-data syndication: you control which items go to each partner, which of their properties are sent and what they're called, and how and how often they're delivered, as JSON or CSV over FTP, SFTP, email, or API. Every send is logged. Live in production at Gumiimpex.
Your partners all want your catalogue. None of them want it in your format.
The problem Proceptio Sync solves
If you sell through partners, every one of them wants your catalog a little differently. One needs the full range as JSON over an API; another wants a trimmed CSV dropped on an SFTP server every morning; a marketplace wants only two brands, with its own column names, refreshed every fifteen minutes. Doing that by hand means a pile of one-off export scripts and a person who remembers to run them - and a feed that is stale the moment it is sent.
A single "export everything" dump does not solve it either: it leaks products and pricing you did not mean to share, in a shape no partner actually asked for. Proceptio Sync turns each partner feed into a managed, scheduled job - the right items, the right fields, the right format and channel, on a cron - so the work happens once at setup and runs itself after that.
One catalogue, every partner's version of it
A product feed is three decisions and a schedule, and Proceptio Sync is easiest to follow as exactly that: choose what this partner sees, choose what the fields are called, choose how and how often it lands, then watch the runs.
JSON · CSV · XLSX · XML, over FTP, SFTP, email or API.
Send only what this partner should see
Scope each feed by category and brand: include a few product groups, send every brand, or send every brand except the ones you keep to yourself. Stock levels can be masked behind a flat number when a partner should not see exact quantities. The count updates as you narrow, so you know what you are about to send.
The same catalogue speaks every partner's language
Choose which properties go into the feed and what each one is called, so an internal SKU arrives as the partner's own field name. Reorder columns, set a default for a field a product leaves blank, and switch off anything a partner should not receive. The output pane shows the feed changing as you edit it.
Set the cadence, the format and the channel
Build the schedule with a picker (every few days, every weekday, at a set time) and the cron expression is written for you. Pick JSON, CSV, XLSX or XML, then one or more channels: pushed to FTP or SFTP, emailed as an attachment, or pulled live from an API endpoint. After setup each feed runs on its own.
Every run is on the record, including the ones that failed
Each run is logged with its timestamp, the list it ran for, how many items went out, and whether it succeeded, so the question "what did this partner receive, and when?" always has an answer. A failed or retried run shows up on the list rather than arriving as a complaint from the partner.
One catalogue, three completely different feeds
Nothing in the product is specific to one industry. The same catalogue serves a marketplace that wants everything hourly as JSON, a trade partner that wants a category as a nightly spreadsheet, and a reseller that pulls a filtered slice live. If you maintain a catalogue and partners need feeds from it, this is the shape of the problem.
Built for any catalog
Proceptio Sync is in production at Gumiimpex, a tyre and vulcanization company, where it feeds product data to marketplaces and trade partners on their own schedules and formats. The same model fits any business that distributes a catalog:
- · Tyre & auto parts
- · Electronics & appliances
- · Building materials & tools
- · Distributors & wholesalers
- · Online marketplaces & resellers
- · Any PIM-to-partner product feed
