Exporters, wholesale suppliers and private-label manufacturers use CatalogX to show a finished piece worn — on a model that suits the destination market, in the colourways you actually cut — the week the sample comes off the table, without booking a shoot per buyer or per season.
An export order is won on a picture long before it is won on a sample. A buyer shortlists from a deck, a linesheet or a WhatsApp message, and what they are looking at is almost always a flat photograph of a garment on a table — because that is what you can produce the day the piece is finished. The shoot, if it happens, happens later, for the pieces that already got interest.
That order is backwards, and everybody in the chain knows it. The flat shot is the one doing the selling and it is the weakest asset you have: it cannot show fall, it cannot show how the sleeve sits, and it cannot show the garment on the kind of body the buyer's own customer has. So the pieces that photograph well get ordered and the pieces that need to be seen worn quietly do not.
The second problem is distance in the literal sense. A buyer in London or Los Angeles is not going to be impressed by a model who does not look like their market, and you are not going to fly one in for a twelve-piece range. Generating the image removes both constraints in the same step: the garment is your real garment, and the model is whoever the destination market expects.
On a table, on a hanger, on a dress form, with a phone. This is the photo you already take the day a sample is approved — nothing new enters the process.
Choose from the built-in catalogue of 58 models, or on Pro and above upload and save your own so every range you send that buyer shares one face and one backdrop.
Batch up to 20 garments per run, file them into a project per buyer, and export the whole thing as one ZIP with a manifest mapping each image back to your own style number.
Every output is named from the file you uploaded it as. Upload EXP-2411-KURTA-NAVY-M and that is what returns — so a forty-piece range arrives already matched to your own numbering instead of as forty files called image-1 through image-40. The ZIP carries a manifest.csv with the source file, the output file, the tool and the generation id, which is what your merchandiser actually needs.
You cut a style in eight colours and photograph one. Colour Variants re-render the same model, pose and lighting with the fabric recoloured, at one credit each, so the buyer sees the full colour story rather than one shot and a Pantone list.
Save a model, a background and a pose, and every range you send that buyer inherits them — this season, next season, and the range you add in between. Up to 20 saved models, backgrounds and poses per account, which for most export houses is one per major account.
If what you ship is sarees, lehengas, kurta sets or sherwanis, the drape is the product. Most virtual try-on was trained on western silhouettes and redraws it: the pallu falls the wrong way, the lehenga flare flattens, the dupatta merges into the outfit. CatalogX measures hem length and anchors it in inches, and treats saree pleating, dupatta fall and lehenga volume as first-class cases.
For an exporter this is not cosmetic. If the generated image shows a block print at the wrong repeat or zari in the wrong place, you have created a dispute between what the buyer approved and what the container contains. CatalogX is built to preserve product pixels for exactly that reason.
You own every output on every plan. No watermarks, no per-image licence, no usage window — which matters because the image does not stop with you. It goes into the buyer's own linesheet, their marketplace listing and their marketing, and nobody wants a licence conversation six months into a relationship.
| 12-piece range for one buyer | Booked shoot | CatalogX |
|---|---|---|
| When it can happen | After the samples are approved and a date is free | The day the sample is finished |
| Model for the destination market | Whoever is bookable locally | Chosen per market, or your own saved model |
| Showing all colourways | One shot and a colour card | Every colourway rendered, 1 credit each |
| A second buyer wants a different look | A second shoot | A second saved model, same garments |
| Style numbering on delivery | Renamed by hand afterwards | Your filenames, plus a manifest |
| Adding a style mid-season | Waits for the next shoot | Runs on its own, same look |
Per-image cost across the plans is ₹12–20 at HD. Full detail on the pricing page.
An export house running several buyers, several seasons and a live sampling calendar is not a self-serve customer for long. The Agency plan is the step for a studio producing on behalf of several brands, and Enterprise is the conversation once the volume is past what a listed tier grants or a team needs onboarding rather than one power user.
The other lever is the API, included from the Business plan up. If your styles already live in a PIM or an ERP, garment photos can go in and finished on-model images come back out without anyone opening a browser — and a verified API key is exempt from both the per-caller rate limits and the per-plan concurrency cap, so a sampling-season batch is not throttled.
The image is photorealistic, and the garment in it is your actual garment rather than an invented one. Beyond that, be straightforward: the disclosure is written into the file automatically on export, so an image showing a photorealistic AI-generated person carries Amazon's contains-synthetic-performer keyword and every export carries the IPTC term for algorithmically generated media. In a B2B relationship, a buyer finding out later is the risk; a buyer being told up front rarely is.
Yes, and it is one of the main reasons exporters use this. The built-in catalogue spans 58 models across different looks and body types, and from the Pro plan up you can upload and save your own so the same face carries across every range you send that buyer.
Yes. Every output is named from the file you uploaded it as, so uploading EXP-2411-KURTA-NAVY-M returns that name. A batch downloads as one ZIP with a manifest.csv mapping the source file, the output file, the tool and the generation id, which is the part that makes it usable by a merchandiser rather than just by a person.
Photograph the one you cut, generate it, then run colour variants at one credit each. The model, pose and lighting stay identical across the run, so the buyer sees a colour story rather than a set of images that look like they came from different sessions.
Yes, and it is built for them specifically rather than adapted to them. Hem length is measured and anchored in inches rather than guessed, and saree pleating, dupatta fall and lehenga volume are handled as first-class cases. If ethnic wear is your line rather than a category in it, test it on your heaviest piece first.
Yes. API access is included from the Business plan up, so garment photos go in and finished images come back out without anyone using a browser. A verified API key is exempt from the per-caller rate limits and from the per-plan concurrency cap, so a sampling-season batch is not throttled — credits remain the only ceiling.
Indian customers are billed in INR with cards, UPI, net banking and wallets; customers outside India are charged in USD on international cards. Every tier below Enterprise is listed openly on the pricing page and can be bought without talking to anyone. Enterprise is quoted against volume and term.
You do, on every plan including the free one, and there is nothing to pass on or renew. No watermarks, no per-image licence, no usage window — so the buyer putting them into their own linesheet, listing or marketing creates no licensing question later.
Five free credits, no card. Use the heaviest, most embroidered piece in the range.