A consistent starting brief
Use a form to collect the product list, required views, specifications and delivery requirements. Flag missing information before the team commits to a shoot plan.
Ecommerce creative production
Move from a client brief to approved production content.
Bring client requirements, brand guidance and production tasks into one process. Let AI prepare working content, give producers a review point, and keep the shoot, editing and delivery stages visible on a shared board.
How can an ecommerce imagery studio use workflow automation?
Collect the client brief and product facts, read the selected brand guidance, and use AI to prepare a production pack. A producer reviews the drafts before they become working instructions and tasks. Track the job on a production board, then prepare a delivery summary and client message when the team confirms the assets are ready.
Connect the preparation, production and handover
This illustrative configuration supports the content and coordination around an imagery job. The studio creates, retouches and approves the images.
Published brand guidance
Give the workflow access to selected documents containing the client's approved tone, product facts and image requirements. Keep draft changes separate from the published reference.
AI-prepared working content
Draft the shoot brief, SKU shot list, retouching instructions and delivery checklist. Include supporting product copy where it is part of the studio's service.
A producer at the review point
Pause the workflow so a producer can inspect and edit the proposed content. The approved branch carries the reviewed information into the next steps.
A shared production board
Connect campaigns, shoots, deliverables and individual tasks. Keep owners, dates, briefs, references and feedback with the work as it moves through production.
A prepared handover
Use a selected status change to start delivery preparation. Draft the asset summary, outstanding exceptions and client message, with a person checking the handover before sending.
Illustrative example
Start with a footwear job the team can understand
A fictional ecommerce imagery studio receives a brief for 12 footwear SKUs, with six images per SKU. The client wants white-background photography showing the front, side, rear, top, upper detail and sole detail, plus short product copy in understated British English.
The brief supplies the delivery deadline, producer responsible, naming convention and image specifications. The requested image set contains 72 assets; the team still needs to check the actual deliverables before release.
For one product, CAN-01, the supplied facts are:
- Product: trainers.
- Colour: sand.
- Upper: canvas.
- Sole: rubber.
- Required views: front, side, rear, top, upper detail and sole detail.
- Approved claims: only the product facts provided.
A form can capture the job name, product list, required views, output specifications, delivery date and known exceptions. A selected document can supply the client's approved brand guidance. Product references and other supporting files can be kept with the relevant tasks.
The workflow should flag missing requirements, such as dimensions or a naming convention, for the producer to resolve. It should not quietly invent them. Explore documents for maintaining the guidance and workflows for connecting the intake and review steps.
Draft a production pack from the facts supplied
An AI step combines the brief with the selected published guidance. Its instructions define the outputs, require consistent SKU references and distinguish client requirements from proposals that still need approval.
The proposed pack includes:
- Shoot brief: the job's purpose, visual requirements, output specifications and constraints.
- SKU shot list: the six required views for each product, with notes drawn from the brief.
- Retouching brief: the client's supplied requirements, plus questions about anything unspecified.
- Delivery checklist: the expected image set, naming convention and exceptions to resolve.
- Optional product copy: headings and short descriptions using verified facts, where copy is part of the service.
For CAN-01, an illustrative draft could contain:
Shot: Side profile on white, showing the complete product and sole.
Proposed filename: CAN-01_side.jpg
Product heading: Sand canvas trainers
Copy draft: Sand-coloured trainers with a canvas upper and rubber sole.
The standing instructions can say: Use only supplied or approved product facts. Flag missing information. Keep suggested creative choices clearly labelled. Do not invent comfort, performance, sustainability or material claims.
Scope the document tool to the appropriate client's guidance. The AI receives the instructions and the tools it is allowed to use, then works within that scope. It does not gain access to every client's material simply because it is working on this job.
Give the producer a clear release decision
Add a Human in the Loop step before the proposed pack is turned into production tasks. The producer checks the views, product facts, requirements and wording, makes any edits, and approves or rejects the content.
The approved branch can save the reviewed pack into a document draft and create the production work. The rejected branch follows the route you configure, such as recording the outstanding questions for a revised submission. Rejection does not automatically create a revision loop unless that path is built.
Saving the pack as a draft does not make it the published reference. If the studio wants the approved instructions published for a wider team, add an explicit publication step with the appropriate document permissions. Otherwise share draft access with the contributors who need it.
Reviewers can respond to configured workflow reviews in the mobile app. Document editing and workflow building take place in the web app.
Keep the shoot and its deliverables on a production board
Use a custom task board with stages such as Brief, Pre-production, Ready to shoot, Shot, Editing, Review and Assets ready. Agree what needs to be true at each hand-off so the labels mean the same thing to everyone.
The board's four levels can be named Campaign, Shoot, Deliverable and Task. The footwear shoot can sit beneath a seasonal campaign, with image-set deliverables and their preparation, selection and retouching tasks underneath it.
After the producer approves the content, a workflow agent with a scoped Task Tool can create or update the appropriate production tasks. Give it access to the selected board and only the actions it needs. A fixed task step is another option when the next action is already known.
Example tasks for CAN-01 include:
- Confirm the sample and supplied product facts.
- Prepare the six-view shot list.
- Photograph the product against the approved brief.
- Select the required views.
- Retouch and check the output specifications.
- Review the image set and supporting copy.
- Confirm the delivery checklist.
Give the tasks named owners and agreed dates, with the pack, references and comments available from the appropriate cards. A producer can mark work blocked while a sample or client answer is missing. Board and document permissions should be chosen for the people involved, with client material kept within the intended audience.
The studio's people update production progress or use explicitly configured workflow actions. A parent status does not, by itself, establish that every deliverable has passed review.
Prepare the handover when the team confirms assets are ready
A Task Trigger can watch for the relevant deliverable entering Assets ready. Configure its filters and subsequent checks so the intended status change starts the handover process, rather than every edit or child-task update.
The next workflow reads the confirmed delivery information and prepares:
- A delivery summary: what the team is handing over.
- An asset checklist: the expected and confirmed deliverables recorded for the job.
- Outstanding exceptions: anything explicitly recorded as missing or awaiting a decision.
- A client email draft: a concise handover message with the confirmed delivery reference.
For CAN-01, the draft could say:
The CAN-01 image set is ready for your review. The handover lists the six approved views and the accompanying product-copy draft. Please use the confirmed delivery location below, and let us know if you have feedback on the supplied set.
The delivery location must come from an actual supplied link or configured system. The workflow must not invent file links or claim that files are present merely because a task changed status. A person checks the assets and message before an Email Send step sends from an authorised mailbox.
If the studio also prepares alt text, an optional image-input step can draft it from explicitly supplied finished images. A person checks the description against the image before use. A planned shot list alone is not evidence of what the finished picture shows.
Connections to an external asset store or ecommerce system need their own compatible integration and permissions. This example does not assume automatic image upload or publication to a shop.
Bring the day's exceptions to the producer
A scheduled workflow can read the selected board and prepare a chat summary of blocked work, approaching deadlines and items awaiting review. Its instructions define the selection window and the information the producer needs to act.
For example:
Production items needing attention
CAN-01: image set awaiting producer review.
CAN-02: preparation blocked while the sample is outstanding.
Check the task owners and agreed dates before confirming the next hand-off.
This is an illustrative summary, not a report from an actual studio. The producer can also ask Butter to find a task, read its latest discussion or help prepare an update, within the access available.
Use the board for the shared flow and each person's task list for their own next actions. Keep recurring delays visible, then adjust the hand-offs and instructions as the team learns.
Explore the platform features behind the process
- Tasks and custom boards: organise campaigns, shoots, deliverables and the work between stages.
- Documents: maintain brand guidance, review working content and publish the chosen version.
- Workflows and human review: connect intake, AI drafting, producer decisions and delivery preparation.
- Workflow builder: configure the steps, connections and triggers on the canvas.
- Butter: work with tasks and supporting information in conversation.
- Mobile app: keep up with tasks and respond to configured workflow reviews away from the desk.
Get the app to continue supported mobile work from your phone.
Questions about creative-production automation
What work does the AI draft in this example?
It prepares the shoot brief, shot list, retouching instructions, delivery checklist and optional supporting copy from the brief and approved guidance. The studio's people create, retouch and approve the imagery.
How do we avoid unsupported product claims?
Provide verified product facts and approved brand guidance, instruct the agent to flag unknowns, and include producer review. Draft copy still needs checking before it is used or supplied to a client.
Does Assets ready automatically verify the files?
No. The status records a decision made by a person or configured process. Use explicit checks and human review before claiming that the required files exist, meet the specifications and are approved for delivery.
Can different client jobs have different access?
Use appropriately shared boards and documents, and scope each workflow agent's tools to the resources it needs. Board access applies to its tasks, while attached documents retain their own permissions. Check those scopes before sharing client material.
Can a production status change start another workflow?
Yes. A Task Trigger can react to selected board events or status transitions. Configure the intended task selection, subsequent checks and loop controls so the handover starts for the right event.
Can the delivery message wait for approval?
Yes. Add a human review point or use the email step's review-before-send setting. The reviewer can check the content before the selected send action proceeds from an authorised mailbox.
Does this workflow choose the shoot schedule or book crew automatically?
The example records agreed dates, owners and production stages. Crew booking, resource capacity and external scheduling require their own verified process or integration. The producer remains responsible for confirming the production plan.
Start with a brief your studio already receives.
Define the content you need, choose the producer's review point and connect the approved pack to the production board. Build the handover around the way your team works.
No card. Your data stays in your organisation.