Short guides to planning your website, organizing product information and deciding who needs access to what.
Choose a guide
Plan your website or store
Start with the visitor's task. Do they need to explore a collection, understand a service or send an inquiry? Choose one main action for each page, then gather the text, photographs and details needed to support it. Prepare each language deliberately; a translated menu alone does not make the whole experience clear.
Planning example
For a furniture workshop, the home page can introduce the work, collection pages can explain materials and sizes, and an inquiry page can ask which piece interests the visitor. If the aim is online purchasing, review the full ordering journey separately rather than treating a product page as a complete checkout.
Before you start
Page list, purpose and next action
Text and licensed photographs for each language
A person responsible for reviewing and updating content
The product describes what you sell. Options describe choices such as finish or size, and a variant identifies a particular combination. Stock quantities answer a different question: how much of that variant is held or reserved in a warehouse? Keep these responsibilities distinct when preparing your records.
Product example
A dining chair offered in natural and dark finishes is one product with two finish variants. Each variant has its own SKU. Preparing those records does not establish a stock balance; review quantities separately for each warehouse.
Illustrative product and variant planning example
Product
Finish
Example SKU
Dining chair
Natural
CHAIR-NAT
Dining chair
Dark
CHAIR-DARK
Before you start
Product names and the options that distinguish variants
A consistent SKU for each variant
Warehouse quantities recorded separately from product descriptions
List what each person needs to manage before choosing their role. A user can belong to more than one organization, and their role is considered within that organization. Review direct permission grants as well as assigned roles; removing a role does not necessarily remove every permission.
Responsibility example
In the workshop example, one colleague prepares product descriptions while another reviews warehouse quantities. Write down those responsibilities first, then use the organization's role and permission settings to review the access each person needs. This is a planning exercise, not a predefined role configuration.
