Separate client listings without juggling shared tools

Begin with the work you would hand over, not with the invoice. You run listings for several clients, and each one wants its own catalogue turned into rows a store will accept. ShopCSV AI does that bulk generation from product data you supply, and it produces title variations aimed at search results. Whether that is worth paying for depends on how much listing admin currently sits with your team.

Value for your agency comes from repetition. Once you know how a client's catalogue behaves, the same pattern applies across their range, and you can hand the output to a reviewer rather than writing each row. The trial credits let you test that pattern on real products before you commit. What you are buying is time back on drafting, not a replacement for the person who checks the copy.

Judge the cost against the tier you actually need, not the largest one. A single client with a modest catalogue may sit comfortably on a smaller tier, while a client with a wide product range and several destinations will draw on credits faster. Map each client's likely volume first, then decide which lifetime tier matches the way your agency works.

The division that matters to you is not between cheap and expensive. It is between tiers that suit your own output and tiers built for someone running a store themselves. Your objection is a shared inbox that mixes clients together, so read the tier descriptions with that in mind. Check what each tier allows and whether the way you separate client work fits inside it.

ShopCSV AI publishes lifetime tiers under the names Creator lifetime, Store lifetime and BYOK Store lifetime. Their detail sits on softwareprogrammer.app, and that page is where you should confirm what each one covers. Read it as a scope document rather than a price list: what volume, what destinations, and what the tier permits. Bring the page to your next internal review so nobody assumes a feature that is not there.

The BYOK option deserves its own line in your notes. If it depends on you supplying your own key, that changes how you plan credentials across client accounts and how you think about running costs beyond the tier itself. Do not guess at the mechanics. Ask the seller directly, then write down the answer, because credentials and client separation are the two things your agency cannot afford to improvise.

Before you pay, run one client's catalogue through the whole path: input, generation, export, review. Use the free trial credits for this. You want to see where time goes and whether the output needs heavy editing. An agency cannot sell a workflow to a client until it knows the review burden. Record how many rows a normal batch produces and how quickly your credits fall, then compare that with each client's monthly volume.

Then check the exports themselves. Each store applies its own rules, so a file that uploads cleanly to one destination may need adjustment at another. Test the destinations your clients actually sell through, not a generic list. Keep a short note per store on what needed changing, because that note becomes your internal checklist and saves the next person the same discovery.

Finally, settle the client separation question in writing. Ask how you keep one client's catalogue apart from another's when you work in the same account, and get the answer from the seller rather than from assumption. Your agency's promise to clients is that their data and their sending stay distinct. If the tier or the workflow cannot support that, the tool is wrong for you regardless of price.

Treat the upgrade as a staged decision. Start on trial credits with one client, move to a lifetime tier once that client's pattern is proven, and only then bring the second and third client across. That order keeps your risk small and gives you evidence for each step. If a client's catalogue is unusual, test it separately rather than folding it into a batch that already works.

Set an internal habit around review. Generated titles and descriptions arrive as drafts, and someone on your side must read them before a client sees them. Decide who does that reading per client and put it in the schedule, because review time is the cost that hides in a listing workflow. A named reviewer per client also answers the separation question in practice, not just on paper.

Keep a short log as you go: which client, which store, what the batch covered, what needed fixing at review. That log becomes the case for staying on the tier or moving up, and it gives you something concrete to show a client who asks how their listings were produced. Revisit the softwareprogrammer.app tier page whenever your client count changes, so the tier still matches the work.