Billing
Vendus integration
Web orders, takeaway and marketplace sales become Vendus documents on the right register, with stock kept consistent.
Overview
Vendus
Cegid Vendus is invoicing and point of sale software found in many Portuguese restaurants, cafés and high-street shops. It runs on tablets, computers and phones, and organises the business into stores and registers, with tables, rooms and kitchen printers for hospitality.
The Vendus API uses one key per user, so everything the connection issues is attributed to that user, like another operator. Each document is created on a specific register, and the API accepts a transaction ID that prevents duplicate documents when a request is sent twice.
Tejobit uses this to bring outside sales into Vendus: web shop orders, takeaway requests, marketplace sales. Documents can come back ready for thermal printing (ESC/POS), so the ticket or order shows up on the store printer.
Use cases
What it is for
- A restaurant taking takeaway orders on its website and printing them in the kitchen.
- A street shop with a website, where online sales draw from the same stock as the counter.
- A small chain that wants each register's end-of-day totals in a shared spreadsheet.
- A kiosk or event stand taking MB WAY payments and issuing simplified invoices automatically.
What the connection listens to
- A paid web order or a confirmed takeaway request.
- An MB WAY or card payment confirmed by the gateway.
- A scheduled end-of-day run to read register movements and balances.
- A product or price change in the system that owns the catalogue.
What the connection does
- Issues a simplified invoice, invoice-receipt or invoice on the chosen register and store.
- Returns the document as a PDF or as ESC/POS for thermal printing.
- Creates or updates customers and products with an external reference linking both systems.
- Issues a credit note tied to the original document when goods are returned.
- Reads register balances and movements for reporting outside Vendus.
How it works
From the request to a working connection
- 01
Request
The form names the integration, the tools involved and what should happen in each case.
- 02
Review and proposal
Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.
- 03
Setup and testing
The connection is set up with the business's own accounts and tested with real cases before it goes live.
- 04
Maintenance and monitoring
Tejobit hosts the connection, follows up on errors and adapts it when the API changes.
The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.
What to prepare
- A Vendus account with at least one active user and an API key from APPS, API.
- A user dedicated to the integration, so its documents are easy to identify.
- Stores and registers set up, and a decision on which register receives each channel's sales.
- Product references matching those used by the web shop or ordering platform.
For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.
Limits
- A document date cannot be earlier than the last issued document or later than today, so late sales cannot be invoiced with their original date.
- Once issued, a document only accepts status, stock or mode changes; anything else needs a credit note.
- Customers must never be sent with the generic tax number 999999990; anonymous sales go out as final consumer.
- The API does not push counter sales to other systems, so the connection reads them from Vendus on a schedule.
Frequently asked questions
Before you start
Can it be tested without issuing real documents?
Yes. Vendus has a test mode, and the connection is validated there before switching to normal mode.
If the website sends the same order twice, do I get two invoices?
No. Each sale carries a transaction ID, and Vendus refuses to create a second document with the same one.
Who reports invoices to the AT?
Vendus, as certified software. The connection only passes the sale along; the document is issued and signed by Vendus.
Related integrations
See all integrations- Billing
Moloni
Every sale paid in another system becomes a Moloni invoice, in the right series and with the customer matched by NIF.
From €5 /month + IVA
See integration - Payments
SIBS e MB WAY
Takes MB WAY, Multibanco and card payments straight through the SIBS Gateway, with webhooks and statuses verified.
From €5 /month + IVA
See integration - Commerce
Shopify
Connects a Shopify store to certified Portuguese invoicing, carriers and stock, driven by order webhooks.
From €5 /month + IVA
See integration
Set up the Vendus integration?
Describe what should pass between the tools. The reply confirms feasibility, price and timeline.