> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/products.md). # Products Products are at the core of everything you do in Flow Retail – from sales and inventory to reports and campaigns. Taking time to set up your product data properly makes daily work smoother and reporting more useful. *** ### Before you add products A few things need to be in place first:

What	Required?	Why
Product Groups	Yes	Required for every product. Used for reporting and campaigns
Brands	Yes	Required for every product. Track performance by manufacturer
Properties	Only for variants	Defines options like size and color for configurable products
VAT codes	For import	Required when importing products. Set up by Flow Retail – contact support if you're missing any

If you're not sure where to start, head to Catalog setup for a checklist. *** ### How do I add products?

Method	Best for
Manual entry	Single products or small batches
Spreadsheet import	Bulk additions, and families of similar products
API integration	Ongoing sync with ERP/PIM

For a range of the same item in different sizes or colours, set it up as a configurable product with variants rather than as separate products. When adding products you can also include images and linked products such as accessories or insurance. Need to look up a specific field? See Product fields reference. *** ### Shortcuts in the Client Use Categories to add quick-access buttons in the Client for products your staff use often – like bags, gift cards, or popular product groups. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flowretail.com/docs/day-to-day-operations/products.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.