POS Integration (Sales → tSpoonLab) | tSpoonLab Learn Center

Why integrate your POS with tSpoonLab?

Integrating your POS allows you to link sales with recipes and stock movements — improving control and reducing losses.

✅ Benefits:

Real-time theoretical stock updates (sales deduct, purchases add).
Calculation of theoretical food cost per period.
Comparison between theoretical and accounting food cost to identify deviations.
Unified menu and sales data across multiple locations.

You can connect your POS in different ways depending on your setup:

• The POS exports a CSV after each shift or periodically. • tSpoonLab fetches it automatically. • Simple, reliable, and compatible with most systems.

• tSpoonLab connects directly to your POS API or receives webhooks. • Requires credentials or access tokens.

• If your group consolidates sales in a central system, tSpoonLab connects there.

💡 Recommendation: CSV over SFTP offers the best balance of stability, traceability, and flexibility.

Get your credentials
→ Request your integration user, password, and connection parameters from our team.
Enable integrations
Go to:
Settings → Integrations → Enable “Generic POS Integration”
and (if needed) Enable SFTP Integration.
Set up a “Sales Client”
- Create or edit a client representing your POS channel (e.g. Restaurant Room, Bar, Delivery).
- Enter your integration parameters.
- Define the transfer time or import frequency.

To match POS sales items with your tSpoonLab products:

Build your menu in tSpoonLab (dishes, drinks, etc.).
In each item, fill in the Sales Code (PLU) that matches your POS article code.
For modifiers or combos, define a parent_article_code and its related items.
Confirm that all products have recipes (so tSpoonLab can calculate ingredient consumption).

🧩 Tip: Keep one PLU dictionary per channel if menus differ (restaurant, delivery, kiosk...).

Field	Description
`date`	Sale date (`DD/MM/YYYY`)
`time`	Sale time (`HH:MM:SS`)
`article_code`	POS article / PLU
`article_descr`	Product description
`quantity`	Quantity sold
`unit_price_excl_vat`	Unit price (excl. VAT)
`amount_excl_vat`	Line total (excl. VAT)
`discount_excl_vat`	Discount amount
`vat_percent`	VAT rate (%)
`parent_article_code`	Parent article (for combos/modifiers, optional)

Formatting rules

• Separator: ; • No quotation marks ("") • First row = header • Filenames must be unique (include date/time)

Type	Description
End-of-day	One CSV per shift/closing.
Real-time	Frequent CSV/API transfers every X minutes.

Set the import time in the “Sales Client” configuration.

Before enabling automatic import:

Test one full day of data.
Review in tSpoonLab:
- ✅ Total sales vs POS
- ✅ VAT breakdown
- ⚠️ Missing/mismatched PLUs
Fix and retry until results align.

Problem	Solution
Product not mapped	Add or correct PLU in tSpoonLab
Wrong VAT rate	Update VAT mapping in POS
Missing modifiers	Add `parent_article_code`
Duplicate files	Use unique filenames (tSpoonLab deduplicates)
Discount not per line	Add separate discount line in CSV

Keep POS and tSpoonLab menus synchronized.
Document PLU updates with each menu change.
Schedule a daily report comparing:
- Sales total
- VAT by type
- Theoretical vs real food cost

(You can replicate this structure for Lightspeed, Square, SumUp, etc.)

Contact our team:
📧 [email protected]
We’ll assist you with: