Setup playbook

How to set up Lasso

Here are six chapters that will take you from an empty workspace to a team using Lasso every week. You can keep this tab open, check steps as you go, and come back to it if needed.

Build your setup prompt

Tell us about your e-shop, and we’ll build you a custom prompt you can use in any AI assistant of your choice to get a practical setup plan.

Shop platform
Shopify
Shoptet
WooCommerce
Other
Catalog size
Under 500
500–2,000
2,000–10,000
Over 10,000
Suppliers
1–5
6–20
21–50
Over 50
People
Just me
2–3
4–10
Over 10

Platform describes your shop. It does not connect it to Lasso.

Supplier data you get
Where your products go
Main problem
Languages you sell in
English
Prompt preview
6,119 characters
You are an expert in e-commerce product data and in the Lasso platform. I run an online shop and I want to set up Lasso from scratch. Please guide me through it step by step, in the order below.

About my shop:
- Shop: my shop
- Shop platform (what my shop runs on, not a Lasso connection): Shopify
- Catalog size: 500–2,000
- Number of suppliers: 6–20
- Supplier data I get: not specified, please assume
- Where my products go: not specified, please assume
- People working on product data: 2–3
- Main problem to solve: not specified, please assume
- Languages I sell in: English

About Lasso:
Lasso (productlasso.com) prepares product data for e-shops. You upload supplier files (XLS, XLSX, CSV, XML, DOCX, TXT, images, and PDF in beta). Lasso extracts the products and maps them to your shop's schema. It fills in missing attributes, either by generating them or by looking them up on the supplier's website, and it fixes or generates product images. Your team reviews the results in a table and marks finished rows with Mark ready. You then export as CSV or XLSX, publish a product feed for Heureka.cz, Zbozi.cz or Google Merchant, or use the API. Shopify products can be imported into Lasso. Lasso handles catalogs of 10k+ products, and there is a free plan with no card needed.
Only suggest things Lasso does as described here. If you are not sure a feature exists, say so instead of guessing.

Lasso building blocks (use these terms and define each one with an example from my shop):
- Workspace: my company's Lasso account, where the team, credits and settings live.
- Schema: the target structure of one product type, best built from my shop's import file.
- Attribute: one field in a schema. Shared attributes are reused across tables. Helper columns belong to one table and hold anything that should not reach my shop.
- Category tree: my shop's categories, uploaded as txt, csv, xlsx, json or xml.
- Table: where extracted products are worked on, column by column.
- Source file: a supplier file I upload for extraction.
- Source Library: shared files, sitemaps and supplier websites Lasso can use.
- Catalog: my finished products, each with a status of Draft, Active or Archived.
- Feed: a product feed for Heureka.cz, Zbozi.cz, Google Merchant, Generic XML or Custom XML.
- User roles: Owner, plus the presets Admin, Content editor, Catalog manager, Developer, or a Custom role.

HOW TO ANSWER
- Start by listing your assumptions about my shop in 3 to 5 bullets.
- Give me one framing idea for my setup in one or two sentences, for example how data should flow from my suppliers to my shop.
- Use tables wherever you list things, and give a type for every attribute.
- Prioritise. Say what to set up now and what to skip for now. Warn me if I am about to build more than I need for a pilot.
- Name the single most consequential decision in my setup. Usually it is the schema built from my shop's import file.
- Link to the Lasso docs (productlasso.com/docs) where they help, for example /docs/learn/schemas, /docs/learn/attributes, /docs/learn/files, /docs/learn/enrich, /docs/learn/exports.
- If you are not sure a Lasso feature exists, say so instead of guessing.

Please help me with these steps:

1. WORKSPACE
Who from my team should join first. The free plan has up to 2 user slots.

2. TARGET STRUCTURE
Start from my shop's real import file. Suggest a schema that stays close to that file, so nothing is left out at export. For each attribute say whether it is Shared (used across tables) or a Helper column (for internal data that should not reach my shop). Suggest a category tree.

3. SUPPLIER DATA
Plan a pilot of 10 to 20 products from one supplier file. Tell me which supplier and file to start with, given the formats I get, and what to check in the result.

4. ENRICHMENT AND IMAGES
For my key columns, write example prompts that use {{column}} references ({{all}} means the whole row). Use identifiers such as EAN or model number, and limit web search to the supplier's official domain. If I sell in more languages, say what belongs in my glossary.
Suggest image rules (aspect ratio, format, background, size) that I should set before I run any images.

5. REVIEW AND PUBLISH
Suggest roles for my team from these presets: Owner, Admin, Content editor, Catalog manager, Developer, or Custom. Explain how to use Mark ready and the Catalog status (Draft, Active, Archived) as our review step.
Then pick the export route that fits where my products go: CSV or XLSX export, a product feed, or the API. If my shop platform has no direct connection, use export or a product feed.

6. SCALE UP
When the pilot is reviewed and exported, tell me how to scale: more suppliers, more team members, feeds.

OUTPUT FORMAT
Please structure your answer as:

0. Assumptions and framing
- Your assumptions about my shop
- One framing idea for my setup

1. Lasso building blocks
- A table: building block, what it is in Lasso, example from my shop

2. Suggested schema
- A table of attributes: name, type, Shared or Helper, one-line description
- Which attributes to create now, and which to skip until after the pilot

3. Category tree
- A suggested tree for my catalog

4. Pilot plan
- Which supplier file, which 10 to 20 products, and what to check

5. Prompt examples
- One prompt per key column, using {{column}} references

6. Image rules
- Aspect ratio, format, background and size

7. Team roles
- A table: person or role on my team, preset role, what they do

8. Export route
- Which export or feed to use, and why

9. The most consequential decision
- What it is, why it matters, and what I should decide

10. Where to start
- Build it in layers that follow these 6 steps: workspace, target structure, supplier data pilot, enrichment and images, review and publish, then scale up and credits. Frame it as a starting point, not a strict plan.
- End with one line I can keep as the guiding principle for my setup.

If my answers leave something open, pick a sensible default for a shop like mine and tell me what you assumed. A concrete suggestion I can change is more useful to me than a question back.

Paste it into the AI assistant you already use.

Your answers and checklist stay in this browser.

Start with a focused pilot

Use this focused pilot to turn one supplier file into 10–20 reviewed products, ready to import into your shop. Before processing your whole catalog, you’ll try the full workflow from creating a schema through enrichment and review to an XLSX export.

Start with your workspace
0 / 4

Create your workspace

Your workspace is your company’s home in Lasso: the team, settings, catalog, and credits in one place. Start with the demo to see what a finished result looks like.

Estimate
3–5 min
Have ready
Work email or Google account; teammate emails
In Lasso
Sign up
0 / 4

Define your shop’s structure

A schema is the blueprint for your product data: it defines the fields each product needs, such as name, EAN, price and description, and the type of data each field holds. Choose how to create it:

Estimate
10–30 min
Have ready
Your shop’s import template and category list
In Lasso
Data Management → Schemas, Attributes, and Category Trees
Open your workspace
  • Learn more:Schemas
  • Learn more:Attributes
0 / 3

Bring in supplier data

Start with from one supplier. A small pilot makes it easier to check the mapping and fix problems before processing a whole catalog.

Estimate
2–10 min + processing
Have ready
One supplier file with 10–20 products
In Lasso
Product Onboarding
Open your workspace
  • Learn more:File uploads
0 / 5

Enrich with AI

Work column by column and give the AI reliable identifiers and sources. First then once the results look right.

Estimate
10–20 min
Have ready
EAN or model, supplier domain, glossary and image rules
In Lasso
Product Onboarding → Your table → Column prompts and image tools
Open your workspace
  • Learn more:AI enhancement
0 / 6

Review with your team and publish

Review the pilot and test a real export before scaling up. Use and to make it clear which products are finished and which still need work.

Estimate
At your own pace
Have ready
Team responsibilities and your import format or feed type
In Lasso
Settings → Team; Catalog
Open your workspace
  • Learn more:Catalog
  • Learn more:Exporting data

Direct integrations are on the way

Exports and product feeds already give you a reliable path into your shop today. Upcoming direct platform integrations will make an already strong workflow even smoother, taking Lasso from excellent to exceptional.

0 / 4

Scale up and track credits

Once the pilot is reviewed and exported, bring in more suppliers and teammates. Keep the same working structure, watch usage and make the process easy to repeat each week.

Estimate
At your own pace
Have ready
A reviewed pilot and a tested export
In Lasso
Credits & Reports; Getting started
Open your workspace

A small pilot today builds a solid foundation for the future.