One product feed. Every marketplace in its own format.
Send your master sheet and photo folders once, kept the way you keep them. The agent writes each marketplace’s listings in that marketplace’s current format, pushed directly where an interface exists and delivered as a checked, upload-ready sheet where it does not. It works for one seller at a time, and wherever a marketplace needs your own click, it says so.
One master sheet in, each marketplace’s listings out.
Four steps, in the order a build runs. Nothing reaches a marketplace before you have seen its first batch.
Your master sheet and photo folders, as they are
Style code, lot, colours and sizes stay the way you keep them. The agent builds from your structure and never regroups or renames it.
Your rules, in writing
Brand, tone, category choices, which marketplaces come first and what must always be asked. One document the agent follows on every product.
A first batch per marketplace, checked
Each marketplace gets a first batch built to its rules and run through the pre-flight check. It comes to you before anything is uploaded.
Upload or approve, then the monthly sync
You click upload where the marketplace requires it; we push where its interface allows. From then on, price and stock are brought into step every month.
How each marketplace is delivered.
Where a marketplace publishes an interface, the agent pushes to it. Where it offers only a template, you receive that template filled and checked. This grid says which is which, so nothing is presented as automatic when it is not.
Shopify
Created directly in your store as drafts. Nothing goes live until you approve it.
Amazon
An upload-ready sheet now, direct push on request. Every product needs a GTIN or EAN, and brand approval applies where the marketplace asks for it.
Flipkart
New products as an upload-ready sheet; price and stock updated directly. The marketplace’s own quality check takes a day or two.
Meesho
An upload-ready sheet with hosted image links. The marketplace’s own check can take up to three days.
Myntra
The marketplace’s upload template, filled and checked. Brand onboarding is handled by the marketplace.
AJIO
An upload-ready sheet. Variants are fixed at the first upload, so they are settled before it; onboarding is handled by the marketplace.
Other marketplaces
Snapdeal, JioMart, Nykaa, Tata CLiQ, WooCommerce, eBay and Etsy on request. The delivery method for each is scoped in the proposal before you commit.
Approval, ranking and orders belong to each marketplace. The agent prepares listings that pass its rules; whether they are accepted and how they rank is the marketplace’s decision.
Eight jobs, done to every product for every marketplace.
Your data is the source of truth. The agent reshapes it for each marketplace and checks it before a sheet or a push leaves us.
Category mapping
Each product placed in the category tree of every marketplace it goes to, starting from your own categories.
Required attributes
Every mandatory field filled from your data, or flagged where your data does not carry it. Nothing is invented to fill a gap.
Titles to each marketplace’s rules
Titles and descriptions written to each marketplace’s length and wording rules, with the search terms its buyers use.
Image renditions
Your photos rendered to each marketplace’s ratio, size and background, then hosted with stable links. You supply the photos; there is no photography.
Pre-flight check
Mandatory fields, controlled values, character limits and row limits tested before anything is handed to you or pushed.
Current templates
Marketplaces change their templates. The agent works from the current one and keeps it current as they change.
Identifier check
GTIN or EAN and tax codes checked before the build, with every gap listed so you can source the code or apply for an exemption.
Monthly sync
Price and stock brought into step across every marketplace each month, from your master sheet.
Four things that stay with you or the marketplace.
A template is never presented as an interface. Where a step needs you, the proposal and the per-product log both say so.
Your seller login
Never asked for. We use partner or developer access if a marketplace grants it; everywhere else the upload button stays in your hands.
The upload click
Where a marketplace demands your own click, the sheet arrives checked and ready, and the step is never described as automatic.
A fact not in your data
A missing fabric, size or code is flagged and waits for your answer. What your sheet says is what the listing says.
Payments, returns and approval
Orders are read, never handled. Payments and returns stay in your own panels; approval and ranking stay with each marketplace.
Everything built comes back to you, filed.
The files are yours. They are handed back after every build and never reused for anyone else.
Sheet exports
One export per marketplace in its current template, plus a master export marking every product as built, flagged or live.
Image folders
Filed under style code first, colour second and marketplace rendition third, then served from stable links; the tidied folder comes back to you.
Inventory and orders read
Directly from Shopify, Flipkart and Amazon through partner or developer access; from a downloaded seller-panel report for Meesho, Myntra and AJIO.
One daily sheet
Every day, stock, orders and returns from all your marketplaces land in a single sheet. Stock goes back directly where an interface exists, or as an upload-ready sheet.
Sent once. Compiled for each marketplace.
Your sheet and photos become one product model inside the agent. The pre-flight check tests it against each marketplace’s rules; from there it is pushed directly where an interface exists, or handed to you as an upload-ready sheet where the marketplace needs your click. The monthly sync keeps price and stock the same everywhere.
Each photo read against its row.
On request, every photo is compared with the sheet row it belongs to and the result comes back as a flag list. The check never edits a product, and if photo and sheet conflict, the sheet is taken as right.
Colour and type
The colour in the photo against the colour code in the row, and the product type against its category.
Quality
Photos that are blurred or too low in resolution for a marketplace rendition.
Duplicates and gaps
The same photo filed under two rows, and rows with no usable photo at all.
Backgrounds
A background that would fail a marketplace’s rendition rules, flagged before the sheet is built.
Four things you always get.
Each marketplace is its own piece of work, with its own template and rules, so the proposal is set out marketplace by marketplace, and adding one reuses the same product data. A product counts as one style, every colour and size included, up to a variant count stated in the proposal. Marketplace fees stay on your own account and are named in the proposal. Every product action is logged per marketplace, and no promise is made about ranking or sales.
A written brief
What we agreed to build, in one document.
A fixed price
Set in the proposal, before work starts.
Staging + approval
You see it and approve it before it goes live.
Documentation
How it works and how to change it, handed over.
Before you send the sheet.
Selling only on your own store? There, the Shopify Catalogue Agent creates this catalogue as drafts. Agencies can ask for terms in writing.
Is this fully automatic?
Not everywhere, and the proposal will not say it is. Where a marketplace publishes an interface, the agent pushes to it directly. Where it offers only a template, you receive that template filled and checked, and you click upload in your own panel. A listing sold as automatic that turns out to be someone typing into your panel with your login is what this service is built to avoid.
Do you need our seller-panel login?
No, never. Where a marketplace offers partner or developer access, that is what we use, and you can withdraw it. Everywhere else the checked sheet comes to you and the upload button stays yours.
What happens when a listing is rejected?
The pre-flight check catches most rejections before a sheet leaves us, and anything a marketplace still rejects is fixed in the revision round. Approval itself is the marketplace’s decision, and nobody outside it can promise it.
Do we need GTIN or EAN codes?
Where a marketplace requires them, yes. We check your data before the build and list every SKU without one, so you can source the codes or apply to the marketplace for an exemption before a build that could not go live.
Not sure what you need? Ask in writing.
Send your sheet and a few photos. The reply carries a checked sample built for your most important marketplace. Agencies can ask for terms in writing.