The template library

If you build stores for clients, the second one looks a lot like the first. The template library turns the first into the starting point for the second.

It lives on the Organizations page, below the store list: "Starting points this organisation offers when a member creates a new store."

Marking a store as a template

On a store your organisation runs, choose Mark as template.

You give it:

Template name — "Fashion starter", say. This is what your colleagues read, so name it after what it is for.

Description — "What makes this a good starting point?"

It then appears in the library: "Members will see this as a starting point when they create a new store."

A template is a real, live store. It is not a frozen snapshot. If you keep editing that store, stores created afterwards pick up the newer version. That is convenient — but it means a store serving as a template is a store to edit carefully.

Using a template

Press Use template, name the new store, and building starts in the background.

Only an organisation's owner or admin can: "Only an owner or admin can use a template."

What does NOT come with the copy

The dialog spells it out, and the list is the same as duplicating an ordinary store:

• Orders
• Customers
• The custom domain
• The team

So a copy carries the design and catalogue, not the trading history. That is exactly what you want: a new client must not see an old client's orders, and must not inherit their domain.

Turned around: whatever is in the template is what every client of yours gets. If the template store still has a test product called "test 123", so will the next client's store. Tidy the template before marking it.

Editing and unmarking

Edit template changes the name and description — it touches nothing in the store's content.

Unmark removes it from the library: "“{name}” will no longer appear in the library. Stores already created from it are unaffected."

A copy is a copy. Once a client store exists it is fully independent — unmarking the template, or editing it, does not reach it.

Platform templates

The /templates page is a different thing: "Starting points provided by the platform. Using one creates a new site from it — after that, everything is yours to edit."

Those are templates for everybody, not your organisation's own. Each has View live so you can look before committing.

Both libraries share the same machinery; they differ in who supplies them.

Section templates are yet another thing

The editor's rail also has a Templates entry. Those are section templates — prebuilt pieces of page you drag onto a page.

Three different things, easily confused:

What	Where	What it creates
An organisation's template library	/orgs	A new store
The platform's Templates	/templates	A new store
Templates on the editor rail	The editor	A section on the current page

An agency's workflow

1. Build the first store properly. This is the investment.
2. Clean it: delete test products, make the placeholder copy read like placeholder copy.
3. Mark as template with a clear name and description.
4. Next client: Use template → name it → wait for the build.
5. Rebrand, swap the catalogue, attach the client's domain.
6. The store owner (or you, if you created it) grants operation to the organisation — see Moving sites around.