How e-commerce teams use AI image generation: accounts, cost and roles for a 10-person team

The identical unit price across all three rows is deliberate — that is the point of the table. Headcount does not change unit price; only volume does. The decision actually rests on the last two columns: whether you need per-person accounting, and which trade-off you can live with.

Rolling it out (four steps plus one standard)

This is the order we suggest for team onboarding. The first four steps are the production line itself; the fifth is what keeps output from drifting once several people are generating.

1. 1

   Step 1: 1. Bring in the product photos

   Name and file the SKU photos under one convention, then batch upload — up to 50 per submission. Settle the naming rule (SKU code works well) at this step, because that is what lets you match finished images back to the right listing later. Skip it and things fall apart as volume grows.

2. 2

   Step 2: 2. Batch generate with scene presets and recipes

   Pick a scene from the 12 e-commerce presets (white-background main image, scene compositing, model try-on, feature callouts and so on) and get one benchmark SKU right first. Once you are happy, save that parameter set and prompt as a recipe and apply it to the rest. This step is what determines whether the whole batch looks consistent.

3. 3

   Step 3: 3. Permanent cloud storage and bulk export

   Finished images and reference images are stored permanently in the cloud, so switching machines or handing over to someone else still gets you the history — nothing depends on one person's laptop. For external delivery or archiving, use bulk export/backup to produce image packs at platform specifications so nobody re-crops sizes by hand.

4. 4

   Step 4: 4. Use the enterprise API when it needs to reach your own systems

   At higher volume or for routine triggering, connect generation to your ERP, storefront or automation scripts through the enterprise API: submit a job, get a task id back immediately, then poll for the result. Idempotency keys are supported so retries do not double-charge. Note that reference images must be publicly reachable https URLs (your own OSS/CDN is fine) — the API channel itself does not provide an upload endpoint. Access is activated by contacting us; see the developers page for how it is called.

5. 5

   Step 5: 5. Keep output consistent with recipes, not longer briefs

   The usual problem with several people generating is not that they cannot use the tool — it is that styles drift apart. Rather than writing an ever more detailed brief each time, save the approved parameter set as a recipe and put brand assets in brand space so everyone starts from the same place. When someone new joins, handing them a recipe works far better than handing them a document.

Procurement FAQ

How should a 10-person e-commerce team manage accounts and cost?

Answer: Since there are no seat fees, headcount itself costs nothing — the only things to manage are volume and attribution. Three options: everyone registers their own account (each pays their own, but assets do not pool), the team shares one account (shared recipes and history, but no per-person accounting), or one account with an API key per person (the only way to split usage by person, up to 5 keys, activated by contacting us). Cost derives directly from ¥0.30 per image: 20,000 images a year is about ¥6,000 on pay-per-image, and subscriptions cost less — see the plans page.

Is there a team plan or sub-accounts? I want to give each of my staff one.

Answer: Not today. We have no team seats, sub-accounts or member invitations, and no permission roles or central admin console — stating that plainly so you do not budget on the assumption that seats exist. The available alternatives are the three in the table: individual accounts, one shared account, or splitting usage with API keys (up to 5). If seat management is a hard requirement for you, contact us with your team size and we will assess from there.

Can several people use one account?

Answer: Technically yes, and many small teams do exactly that — the upside is that recipes, brand space and history are shared automatically. Be clear on the cost though: credentials have to be shared, there is no per-person audit trail, concurrent logins across devices carry security risk, and when someone leaves there is no way to revoke just that person (only a password change). If you need per-person accounting or have audit requirements, use API keys to split usage instead.

Can you issue an invoice? Do you accept bank transfer?

Answer: Contact us with your invoicing entity and requirements and we will answer based on your situation. This page does not commit to an invoicing process or to bank transfer — if either is a hard prerequisite in your procurement process, confirm with us first, then decide how to purchase.

We have high volume, or we need self-hosting / SSO. How do we discuss that?

Answer: If you need separate billing per department or legal entity, seat management with a central console, SSO, or you want to connect generation to your own systems well beyond the default rate limits, contact us with your volume and use case rather than working around the self-serve pages. We do not have those capabilities today; whether and how they can be done depends on your specific scale. What is on the public pages is everything there is right now.