> 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/integrations/erp/sap-business-one.md).
# SAP Business One
How Flow Retail works with SAP Business One, with a local partner running the integration.
Flow Retail works alongside SAP Business One. A local SAP Business One partner builds and runs the integration; Flow Retail provides the API and technical support.
## How it fits together
## What is exchanged
| Data | Direction | Note |
| ------------------- | ----------------- | -------------------------------------------- |
| Products and prices | SAP → Flow Retail | SAP Business One is master |
| Stock | SAP → Flow Retail | When SAP Business One owns inventory |
| Purchase orders | SAP → Flow Retail | |
| Goods receipts | Flow Retail → SAP | When goods are received in store |
| Sales | Flow Retail → SAP | Each sale, as it happens |
| Payments | Flow Retail → SAP | Mapped to account numbers per payment method |
The exact scope is agreed per customer with the partner.
## Getting started
Contact our retail specialists. We put you in touch with the partner and give them access to our API and test environment.
*Last updated 25.09.2026*
---
# 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/integrations/erp/sap-business-one.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.
