Connect Recipok to your invoicing, accounting or POS
All plans
Which data can be synchronised with the software you already use, which connectors are ready and how we build a custom integration.
What it is for
Recipok knows what happens inside the bakery: what you buy, what you produce, with which lots and who you deliver it to. Your invoicing software, your accounts or your POS know what happens in the office and at the counter. If they don’t talk to each other, someone ends up typing the same delivery note, the same customer or the same price twice, and the errors show up at the end of the month.
That is why we connect Recipok to the software you already use. This article is for the owner or manager who wants to know what can be synchronised, how we build a custom integration and what we need from you to get started.
What can be synchronised
An integration moves data in one or both directions. These are the cases bakeries ask us for most:
| Data | Usual direction | What it is for |
|---|---|---|
| Customers | Both directions | You create a customer once, with their tax ID and address, and they exist in both programs. |
| Sales orders | From your online shop or your software to Recipok | The order arrives in Recipok by itself and turns into production. |
| Delivery notes | From Recipok to your invoicing | Each confirmed dispatch, with its lot and price, arrives ready to invoice. |
| Prices and products | From Recipok to your invoicing or POS | Your recipes exist as products with their reference, retail price and VAT. |
| Stock | Depending on the case | What is in the warehouse is checked from the other software or adjusted from it. |
| POS sales | From the POS to Recipok | What is sold at the counter deducts the finished product and appears in your reports. |
| Purchases | From Recipok to your accounts | Goods-in records travel as supplier delivery notes. |
12 cheesecakes for Friday.
They are produced with their lot and delivered with a delivery note.
With customer, lot, price from their price list and VAT.
- 1In: the order arrives from another program and appears in Orders as if you had typed it yourself.
- 2Out: the delivery note confirmed in Recipok travels to your invoicing software.
Connectors that already work
In your account menu, at the top right, Integrations brings together the ready-to-use connectors (the manager and the administrator can see it):
- Holded: customers, suppliers, sales orders, products, goods-in and dispatches. We explain it in Connect Recipok to Holded.
- Dobbox: temperature sensors that create the HACCP records for your cold rooms automatically. It is set up with the email and password of your Dobbox account.
- API Token (Integral plan): the key that lets another program read and write in Recipok. See Public API and tokens.
For stores with the Ágora POS there is a connection in preparation: it sends the bakery’s stock to each store as incoming delivery notes. We explain it in Connect Recipok to the Ágora POS.
How we build a custom integration
When your software has no connector, we build it. The process is always the same:
You tell us what you use and what you want to flow
In the chat or on a call. What matters is the goal: “I never want to type delivery notes again” or “I want what is sold at the till to deduct the stock”.
We look at your software
We check whether it has an API, whether it exports or imports files and what data it allows. With that, we tell you what is possible, in which direction and how often.
We send you a proposal
Which data is synchronised, when, and what must be set up correctly beforehand (customer tax IDs, product references). We don’t start without your go-ahead.
We test it with your data
First with a few real documents. You compare what arrives with what you expected and we adjust it.
We launch it and keep an eye on it
If a synchronisation fails (an expired key, a customer without a tax ID), we detect it and let you know.
What information we will ask you for
- The name and version of the software, and whether it is in the cloud or installed on a computer.
- Who maintains it for you: the company or IT person to talk to if a key or a permission is needed.
- Which data you want to flow and in which direction: customers, orders, delivery notes, prices, stock, sales.
- How many transactions you have: orders per day, delivery notes per month, products in the POS.
- A couple of sample documents: a delivery note, an invoice or an export, so we can see how you name customers and products.
- How you identify your products: if you use references or barcodes, they should be the same in both programs.
Before connecting, check that your customers have the right tax ID and legal name and that your recipes have their SKU or reference. That is what allows the same customer or product to be matched in both programs without duplicating it.
Tips
- Start with a single flow, the one that takes up most of your time (almost always delivery notes), and extend it later.
- Decide which program is in charge of each piece of data. For example: prices are changed in Recipok and the other program receives them.
- If you are going to move recipes or ingredients from a spreadsheet, do it before connecting. We explain it in Moving your recipes from Excel to Recipok.
Tell us which software you use and what you would like to stop typing. We will reply in the chat with what can be done in your case.