Mercer

Fashion concepts and collection coordination

Mercer, formerly CALA, combines AI-assisted fashion imagery with a shared workspace for developing collections. Independent designers and fashion teams can generate a visual direction, revise designs, organise supporting files and communicate with collaborators or production partners. The CALA website redirects to Mercer, whose homepage explicitly identifies the former name.

The product is useful when a collection involves more than generating individual pictures. A design team needs to connect references, decisions, feedback and responsibilities. Mercer brings those activities alongside its image tools, while the designer remains responsible for deciding what the garment should actually be.

Generate and revise a design direction

The feature guide documents text-to-image design, natural-language edits and sketch-to-image rendering. A sketch can become a visual presentation, while the edit tool lets you describe a change to a product design. Swatch generation and application help explore fabrics or prints, and background removal prepares product imagery for further presentation.

AI Influences adds a brand-specific reference workflow. The help centre explains uploading images to train a team-owned Influence and applying it to subsequent generations. Influence slots and training allowances depend on the plan. Reference-led generation can help communicate a visual identity, but it does not guarantee exact reproduction of construction details or fabric behaviour.

Keep feedback attached to the collection

Mercer stores collection assets and supports comments, notes and measurements on creative or technical files. Its published workflow includes sharing collection links and print-ready PDFs with people outside the account. Task tools support assigning responsibilities, timelines and reviews where included in the subscription.

That combination is relevant to teams working with their own manufacturers. A comment attached to a particular design is easier to interpret than an isolated message about an unspecified version. Keep a clear distinction between a visual suggestion, an approved design and the technical specification sent for production.

A capsule-collection example

Imagine a small label developing three lightweight jackets for a spring capsule. Start a Mercer collection with your own sketches and approved references. Generate several interpretations of one silhouette, then revise the preferred concept to explore a shorter collar and an alternative pocket treatment.

Add the proposed fabric direction and write comments identifying which details are intentional. Ask a collaborator to compare the three colourways, and record the selected version before sharing the collection with the production partner. Put unresolved questions, such as fastening construction or lining choice, into explicit tasks. A pattern maker should translate the agreed design into a technically suitable pattern and sample; the image alone cannot settle those decisions.

Plans and manufacturing scope

The pricing page offers paid Designer, Studio, Studio Pro and Enterprise plans with different AI allowances, seats and collaboration tools. Check the current allocation for image generation, Influences and training before planning a collection-wide workflow.

The official FAQ is explicit that Designer, Studio and Studio Pro do not include producing or manufacturing your designs. Production services and access to Mercer's manufacturing network belong to the Enterprise offering. Product templates are described as coming soon, so they should not be counted as a currently included capability.

What still requires specialist judgement?

A plausible render is not evidence of fit, a reliable cost estimate or a production-ready specification. Check garment proportions, seam placement, fabric scale and consistency between views. Use references you have permission to upload, review sharing settings for unreleased collections and confirm the production partner understands which files are approved.