Elbuz pulls paid receipts and customers from your Dotykacka POS and sends back categories and products: no retyping sales, and the POS sells your catalog.
When you need this:
- Your store uses Dotykacka — each paid receipt becomes a sales invoice, cash receipt and customer order.
- Customers buy in store and online — POS customers join your contacts without duplicates.
- Prices and names live in Elbuz — an export template creates and updates POS products.
- The POS has a long history — sales are imported only from your switchover date.
Where to start: get the cloud ID and refresh token from Dotykacka and create a “dotykacka.pl (POS)” template.
What the POS connection does
- Import of paid receipts — each receipt becomes three documents: stock write-off, cash received and the sale.
- Cards for new products — a line item that isn't in your catalog becomes a card in a service category.
- Payment methods — cash, card, transfer and online payment map to your payment methods.
- Customer list — new POS customers are added as contacts without duplicates.
- Export to the POS — categories and products from Elbuz appear and stay updated on the POS.
What you need from Dotykacka
Two values: the cloud number (shown in the account URL after /cloud/) and a refresh token created in the cloud account, in the API access settings.
Dotykacka issues a long-lived refresh token that can't make requests by itself: it is exchanged for short-term working access. Elbuz does this exchange automatically before every operation — that's why the template stores the refresh token, and you never have to renew anything daily.
POS documentation: Dotykacka API.
How to connect
- Create an import template of type “dotykacka.pl (POS)” and fill in “Instance ID (api_instance_id)” and “Token”.
- If the POS has a long history and you only need sales from a certain day, enter that date before the first run in “Import orders from date (YYYY-MM-DD)” under “Advanced” (scenario). If the field is empty, the POS returns its entire history.
- Click “Import” when you can review the result right away: the first run is the largest.
- Check the log and documents (what to expect there), then put the template on a schedule.
- If you manage your product range in Elbuz, set up a separate “dotykacka.pl” export template (how).
Which receipts and customers are imported, and what they become
Elbuz takes only paid sales receipts. Everything else — drafts, internal documents, unpaid bills — is skipped: your records need the sale itself, not intermediate states of a POS shift.
Regular runs pick up receipts created since the previous import, going back an extra twelve hours for clock differences and POS-to-cloud sync delays. Already imported documents aren't duplicated.
One receipt, three documents
A POS sale has three consequences: goods left the warehouse, money came into the till, and the sale counts toward revenue. So Elbuz creates three documents from each receipt:
| Document | Purpose |
|---|---|
| Sales invoice | Writes the sold goods off stock |
| Cash receipt | Records the money received for the receipt |
| Customer order | Records the sale itself: revenue and line items |
After the first import you'll have three times as many documents as receipts — that's expected. The receipt number ties them together: all three show it in the “Document number (site)” column. Each has its own internal identifier (“External document ID”) — otherwise Elbuz would treat them as one document and create only the first.
All three are created unposted: the “Posting status (signatures)” column is not set. The import itself makes no stock movements — the write-off and other effects appear when the document is posted.
A customer order from a receipt does not reserve goods, even when posted and “Paid”: they were handed over at the POS, so there's nothing to hold. The sales invoice writes them off stock. Receipt statuses, totals and sales analytics stay the same. What uses up reservations — see reservations.
All three documents go to the service contact “End consumer”, created once on the first import if it doesn't exist yet. The customer from the receipt isn't carried into the document (why this matters).
Payment methods
The POS sends the payment method as a code, and Elbuz maps the main ones to its payment methods:
| Payment at the POS | Payment method in Elbuz |
|---|---|
| cash | Cash |
| payment card | Bank card |
| bank transfer | Bank transfer |
| online payment | Online payment |
Dotykacka knows about fifty more methods — meal vouchers, gift certificates, QR code, food delivery services (Glovo, Bolt Food, Wolt, Foodora and others). Elbuz keeps their names in the document as is, so reports show where the money came from. The payment status is always “Paid”: a receipt is paid by definition.
What happens to POS customers
Before receipts, Elbuz pulls the POS customer list — people registered for discounts and loyalty programs: first and last name, phone, email, address, postal code, country, city, date of birth, points and a note.
Only new customers are added, to the customer group. Elbuz matches them against its contacts by POS identifier, phone and email. Emails are compared in canonical form, so ivan.petrov+shop@gmail.com and ivanpetrov@gmail.com count as one address, and a customer buying in store and online won't be duplicated.
POS numbers are normalized: nine digits without a country code get the Polish code 48, for the main scenario — a store in Poland. Enter other countries' numbers at the POS in full, with the country code: they are then saved unchanged and matched correctly with existing contacts.
- Existing customers aren't updated: a phone or address changed at the POS isn't written to their card — copy such changes manually.
- The customer doesn't get into documents: the POS customer list and sales documents sit side by side but aren't linked. To see a specific customer's purchases, set the contact in the document manually.
- The “Contact group” field under “Advanced” in the template sets the group only for “End consumer” when it is created; it doesn't affect new customers.
How receipt lines are matched to products
From each receipt line Elbuz takes the name, quantity, price including VAT, line total, discount percentage, unit of measure, the product's POS number and its POS category number. It looks for a catalog card for the line like this:
- by the POS product number — it's saved to the card after the first import, so a known item is found right away;
- by an exact name match with the card name in the catalog.
A found card is not changed: importing a receipt won't touch its price, stock or name.
If nothing is found, a new card is created: the name and price from the receipt (including VAT, as sold), the line quantity as stock, and the unit of measure. The card is created enabled, with “In stock”, but without the “Export to file (to website)” flag: it won't go to your storefront or marketplaces by itself.
- Start or end
- Action or result
- Decision: the path depends on the answer
The document line keeps what was rung up at the POS for good: name, quantity and receipt price. A later catalog price change won't affect an imported receipt — the document records the fact of a sale.
Where new products from the POS go
The POS sends a category number, not a name. Elbuz compares it with the external field of your categories and uses your branch only if they match. The export doesn't fill this field — it keeps its own POS link. Usually nothing matches, so unrecognized items go to a service category “Products - ‹source code› - ‹your template name›”.
It's created disabled and excluded from exports. Later imports put new items into the same category and don't touch its flags — if you enable export for it manually, it stays enabled.
Move cards from there to your own categories freely: a repeat import doesn't change a product's place in the tree, and document lines don't reference the category.
Deleting a category removes from the database all products for which it's the main category — with their descriptions, photos, specifications and questions. Lines of imported documents remain, but the card they reference is gone. Move the cards first, then delete the category; the next run will create it again as soon as an unknown item comes from the POS.
How to export products from Elbuz to the POS
With a separate export template of type “dotykacka.pl”, Elbuz creates categories and products from your catalog on the POS. Categories go first, then products; new records are created, existing ones updated. Elbuz remembers the link, so a repeat export doesn't create duplicates on the POS.
- Request or action
- Reply
- alt — one of the options, depending on the condition
- loop — repeats
- Note
- What's exported. Only products with the “Export to file (to website)” flag whose category is also enabled and marked for export. That's why cards created from receipts are not exported.
- Two prices. The POS stores prices with and without VAT separately, so Elbuz calculates the price without VAT from the product's tax rate.
- Units of measure. Dotykacka accepts only its own fixed list (piece, kilogram, liter, meter and so on); your units are mapped to it, and anything unrecognized becomes a piece.
- What's overwritten on the POS: name, category, unit of measure, barcode, visibility, VAT rate, price with and without VAT, color. The POS always gets a zero discount and the “deduct from stock” setting turned off: stock stays with Elbuz, and the POS will sell an item even at zero quantity.
Categories go first for a reason: a product is sent with its POS category number, and that number exists only after the category is exported. So in the “What to export” section, turn on both “Categories” and “Products”.
If the POS rejects new records, its rejection message goes to the run log. Elbuz doesn't check the POS response to updates, so a failed update goes unnoticed. Before updating, Elbuz asks the POS for the current version of the record batch; if none comes back, the batch is skipped with an orange line in the log (details).
Don't enable export for a card that came from a receipt: the product already exists on the POS. The export doesn't see the link saved by the receipt import — it looks for its own. So the POS receives the card as a new record, and a second product with the same name appears on the POS.
Scheduled updates and repeat exchanges
The POS doesn't notify Elbuz about new receipts: they're picked up by running the template — with the “Import” button or on a schedule. Each run takes receipts from the date of the last imported one minus 12 hours and moves that date forward itself. How to schedule a template and what disabling does — see the data import overview.
What a repeat exchange overwrites
The exchange goes both ways, and the rule is asymmetric:
| What | What a repeat run does |
|---|---|
| An already imported receipt — three documents | Doesn't touch it at all: the document is found by the receipt's POS identifier; status, total, lines and contact aren't rewritten |
| Product cards in Elbuz | Doesn't rewrite price, name, stock or place in the tree; updates only the quantity sold — it's recalculated across all customer orders |
| Products on the POS | The export overwrites every time: price, name, category, VAT and visibility changed on the POS revert to Elbuz values without warning |
Keep items you manage on the POS out of the export — clear “Export to file (to website)” on their cards. There's no other protection: the “Do not update” and “Fixed Price” switches on the product card apply to imports into Elbuz, not exports from it.
When a receipt is canceled or a product is gone
- A receipt disappeared from the POS. The three documents in Elbuz stay as they were: the import can only create documents and writes no line about a missing receipt to the log. Remove such documents manually (how).
- A return was made at the POS. It comes in only if the POS issued it as a regular paid receipt — then as the same set of three documents. Any other record type is silently filtered out, and you make the reverse movement in Elbuz yourself. A return doesn't change the already imported sale documents.
- A product was removed from Elbuz. It stays on the POS as last sent: the export sends no delete commands. The same happens if you clear “Export to file (to website)” on the card. Remove the item in the POS itself.
Run limits
- How many receipts at a time. No cap. Customers and receipts come in pages of 200 records, receipt lines together with the receipt; pages are fetched while the POS reports there's a next one.
- For what period. Receipts created after the date in “Import orders from date” minus 12 hours. If the field is empty, there's no date filter and the POS returns its entire history, so the first run is noticeably larger than the next ones.
- The export sends batches of 100 records: creates first, then updates. Before each update batch, Elbuz requests the same 100 records from the POS — without this it won't accept the change.
- In a demo account, the export is limited to the first 100 categories and 100 products; a production account has no such limit.
How to check a run and fix a mistake
The run log opens in the Operations center — a right-hand panel that doesn't block your work: you can close the template card and follow the run from anywhere.
- Request or action
- Reply
- alt — one of the options, depending on the condition
- Note
Log lines appear in this order:
- “Total contacts imported: N” — how many customers from the POS list were new. No new ones — no line.
- “Requesting a list of orders” — work on receipts starts.
- “Orders received: N” — not the number of receipts but the number of rows that came from the POS: three per receipt, that is, three times more, including receipts already in the database.
- “Total items imported: N” followed by “Product indexing” — how many new cards were created from receipt lines. No new ones — neither line appears.
- “Total orders imported: N” — how many documents were actually created. This is the key number of the run; no new receipts — no line at all, and that's normal.
- “Updating values based on formulas” and “Data import completed!” with “Time spent”.
Find the receipts themselves in the “Documents” window:
- “Source: name” — your template name;
- “Document type” separates the three;
- “Document number (site)” — the POS receipt number, the same in all three;
- “Date added (source)” — the receipt time at the POS.
New cards show in the “Products” window by the “Source: name” column, new customers in “Contacts” by the “Source - name” column. For a longer history, use the “Run history” button in the template card header.
If the wrong data was imported
You can't stop a run midway. The “Stop” button sets a stop flag, but the POS exchange checks it only once, at the very start. Clicked mid-run, it writes “Operation aborted by user!” to the log, but the import runs to the end. The flag is cleared at the start of the next run.
Everything a run created is tagged with its source, so you can filter it:
- Documents — the “Documents” window, the “Source: name” column equals the template name. Select the rows and delete them in bulk; bulk delete skips posted documents and shows how many were skipped.
- Products — the “Products” window, same column. The filtered set includes only cards this import created; it didn't change existing ones.
- Contacts — the “Contacts” window, the “Source - name” column: customers from the POS list.
Deleted documents stay in the “Document trash” for 30 days, and you can restore the whole batch from there.
Deleting documents doesn't roll back the marker of where to continue. The next run starts from the date of the last imported receipt and won't pick up the same receipts again. To re-import a period, enter the date manually: template card, “Advanced” section, “Import orders from date (YYYY-MM-DD)” field.
1
Import orders from date2
Contact group- Import orders from date (YYYY-MM-DD) — the date from which the run picks up receipts.
- Contact group — the group assigned to the end consumer.
Scenarios
In-store sales in the same documents as website orders
Goal: see POS sales in Elbuz next to your online store orders.
What to set up: an import template of type “dotykacka.pl (POS)”, with the “Token” and “Instance ID (api_instance_id)” fields in the “Connection” section; run it with the “Import” button.
Result: each paid receipt becomes three documents — “Sales invoice”, “Cash receipt”, “Customer order” — for the “End consumer” contact. Stock of existing products changes only after the documents are posted; unpaid receipts and other record types are not imported.
Records from a certain day, not the entire POS history
Goal: the POS has been running for a long time, but in Elbuz you need sales only from your switchover date.
What to set up: before the first run, in the template card under “Advanced”, enter the date in “Import orders from date (YYYY-MM-DD)”.
Result: receipts created after that date minus 12 hours are imported. After the run, the date in the field moves to the latest imported receipt, and the next run continues from there.
Regular POS customers in your contact base
Goal: customers registered at the POS for discounts and bonuses should be in the same base as website customers.
What to set up: nothing extra — the same “dotykacka.pl (POS)” template pulls the customer list at the start of every run.
Result: new customers are added to the customer group; those Elbuz already knows by POS identifier, phone or email won't become duplicates. A customer with neither phone nor email isn't added at all, and the customer isn't set in documents from receipts.
Product range from Elbuz on the POS
Goal: prices and names are managed in Elbuz, and the POS should sell at them.
What to set up: a separate export template of type “dotykacka.pl”, with “Categories” and “Products” checked in the “What to export” section. Products need the “Export to file (to website)” flag, and their category must be enabled and marked for export.
Result: categories appear on the POS first, then products; later exports update the same records. A product removed from the export or deleted in Elbuz won't disappear from the POS by itself, and the POS won't deduct stock on sale.
What to do when receipts don't come in
| What you see | Why | What to do |
|---|---|---|
| “API token not specified” | The “Token” or “Instance ID” field is empty | Fill in both fields (where to get them) |
| A rejection message from the POS in the log | The POS didn't accept the token | Create a new refresh token in the cloud account and paste it into the template |
| “Orders received” is there, but “Total orders imported” isn't | No new receipts — everything received is already in the database | Nothing: this is a normal result of a repeat run (log) |
| Not all receipts were imported | Only paid sales receipts are imported, and only after the date under “Advanced” minus 12 hours | Check the receipt type and payment at the POS and the date in the template (which receipts) |
| Two products with the same name on the POS | A card that came from a receipt was enabled for export | Clear “Export to file (to website)” on the card and delete the extra record on the POS (export) |
| “Dotykačka: the POS did not return the record version (ETag) — the update batch was skipped and will be retried on the next run.” | The POS didn't return the current batch version and won't accept changes without it | Wait for the next export or run it again |
| “Operation aborted by user!”, but documents appeared anyway | The stop flag is checked only at the start of the exchange | Remove the extra records by filtering on the source (how) |
| Customer phone numbers got the code 48 | Nine digits without a country code are normalized to Polish format | Enter numbers at the POS with the country code (customers) |
FAQ
Where do I get the Dotykacka instance ID and token?
The instance ID is your cloud number, shown in the account URL after /cloud/. The token is created in the cloud account, in the API access section: it's a refresh token from which Elbuz gets working access itself.
Why does one receipt create three documents?
A POS sale has three consequences: stock write-off, cash received and revenue. All three documents have the same receipt number in the “Document number (site)” column (more).
Are products from the POS created in the right category?
No: the POS sends the category as a number, and new items go to a service category — disabled and excluded from exports. Move cards from there to your own categories (service category).
Will a repeat import overwrite my changes in documents?
No. A run doesn't touch an already imported receipt at all and doesn't rewrite product cards either. The export, however, overwrites the POS (what gets overwritten).
Why do documents show “End consumer” instead of the POS customer?
Elbuz doesn't carry the customer from the receipt into the document. The POS customer list comes in separately, as contacts; to link a sale to a customer, set the contact in the document manually.
How do I remove receipts imported by mistake?
In the “Documents” window, filter rows by the “Source: name” column and delete them in bulk; deleted items stay in the “Document trash” for 30 days. To re-import a period, enter the date under “Advanced” (step by step).
Where to find it and who has access
- Menu
- Directories → Operations → Data import
- Template type
- “dotykacka.pl (POS)”; for export to the POS — the “dotykacka.pl” export template
- Access right
- the “Import” window in group permissions
- Have ready
- The cloud and an refresh token from your Dotykacka account
No file is needed. You fill in two fields in the “Connection” section:
| Field | What to enter |
|---|---|
| Instance ID | Your Dotykacka cloud number (cloud ID). You can see it in the account URL after /cloud/ |
| Token | The API access refresh token created in your Dotykacka account |
1
Token field2
Instance ID (api_instance_id) field- Token — the till's refresh token.
- Instance ID (api_instance_id) — the number of the cloud the till belongs to.
Related topics
- For the big picture of how orders from different systems become documents — Importing orders via API.
- If POS documents need to be posted to write off stock — Customer order.
- To understand how import and scheduling work in general — Data import overview.
