Functions

How to connect Oblio with easySales: a complete setup guide

By easySales Team · Updated 11 September 2026 · 2 min read

How to connect Oblio with easySales: a complete setup guide

Connect Oblio to easySales: the three credentials, what Use stock source really does, invoice and receipt series, the Oblio-only advanced options, and what each Oblio refusal means.

What connecting Oblio gives you

With Oblio connected, easySales issues the invoice for an order, sends it to the customer, marks it as paid, cancels or storno-s it and can keep Oblio's own stock in step — without you opening Oblio at all.

This guide covers the whole connection, including the one setting that decides whether your invoices go out at all.

Before you start

✓

An Oblio account with API access

The token is issued on the account settings page in Oblio. If there is no token there, the plan does not include API access and the connection will fail with You are not allowed to use this API.

✓

Your CIF as Oblio has it

The company registration number is matched against the companies in your Oblio account, not just validated for shape.

✓

The invoice series, created in Oblio

easySales sends the series the order carries. Any series it might use has to exist in Oblio first, otherwise no invoice is issued.

✓

A decision about stock

Whether Oblio's warehouse should be drawn down when an invoice is issued. If yes, the warehouse has to be accurate — a short stock in Oblio stops the invoice.

Step 1 — Open the Billing Software page

Go to Integrations → Billing Software and search for oblio.

The Billing Software page in easySales filtered to Oblio, showing the Oblio card with a Connected state and an Edit button.
The Oblio card on Integrations → Billing Software.

Press Connect on the Oblio card. If you already have a connection, press Edit.

Step 2 — The three credentials

The Oblio connection form in easySales showing Connection name, Company registration number, Username (Email), Token, Use stock source set to Yes, Warehouse name, Workstation name and Receipt series.
The connection. The three starred fields are all Oblio needs; everything below them changes what the invoice looks like.
Field What it is
Connection name Your own name for this connection. It never reaches Oblio.
Company registration number The CIF of the company invoicing, exactly as Oblio has it. It goes out with every request as cif, and a company Oblio does not recognise fails with The company with cif … does not exist.
Username (Email) The e-mail address of the Oblio account. Oblio uses it as the API client id.
Token The API secret from your Oblio account settings. Not your Oblio password.
The three required fields

Step 3 — Decide about stock before you save

Use stock source is the most consequential field on this form, and the Romanian interface names it better than the English one does: Descarcă din gestiune la facturare — take the goods out of the warehouse when invoicing.

Step 4 — Series, workstation and the rest

Field What it does
Use stock source Yes makes every invoice also take the goods out of Oblio's warehouse. See the warning above.
Warehouse name The Oblio gestiune the goods come out of. Optional, case sensitive, and needed in practice as soon as Use stock source is on or you keep more than one warehouse.
Workstation name The Oblio work point the document is issued from. Optional, case sensitive.
Receipt series The series Oblio should use when a payment is collected as a receipt (Chitanta). Ignored for every other collection type.
Send price updates Sends price changes from easySales to the matching Oblio product. Required — the form will not save without an answer.
Use product description Puts the product description on the invoice line instead of only the name.
Template The mentions line printed on the invoice.
The rest of the connection
The lower part of the Oblio connection form showing Send price updates, Use product description and the Template box with its order variable buttons and the Save button.
Send price updates has to be answered before the connection saves.

The Template box sets the mentions line printed on every invoice from this connection. The buttons above it insert values from the order — order ID, platform, observations, AWB number, courier name, payment method.

Step 5 — Advanced options

Everything here is optional, but four of these exist for Oblio alone and one of them prevents duplicate invoices.

The advanced options of an Oblio connection showing Invoice language, Issuer CNP, Issuer name, Due date and Payment type.
The first half of the advanced options.
Option What it does
Invoice language Forces one language for every invoice. Left empty, easySales uses the language of the shop or marketplace the order came from when Oblio supports it.
Issuer CNP and Issuer name Printed on the invoice as the person issuing it. The CNP is validated as exactly 13 digits.
Due days How many days after issue the invoice is due.
Payment type Forces the collection type Oblio records — Chitanta, Bon fiscal, Card, Ordin de plata and the rest. Left empty, easySales derives it from the order's payment method. Choose Chitanta and the Receipt series above is used.
Choose product name Which name goes on the invoice line: the product's own name or the one from the order.
Autodetect district Works out the Bucharest sector from the address when the order does not carry one.
Generate unique discount code Oblio only. Sends each discount as its own coded line rather than merging them.
Set reverse tax Oblio only. Marks the invoice as reverse-charge.
Send vat name only for 0% tax Oblio only. Sends the VAT-exemption name on zero-rated lines only, instead of on every line.
Enable idempotency key Oblio only. Stops a repeated request creating a second invoice for the same order.
Advanced options worth setting
More Oblio advanced options: Choose product name, Autodetect district, Generate unique discount code, Set reverse tax, Send vat name only for 0% tax and Enable idempotency key.
The four options that exist for Oblio alone, and the idempotency key that prevents duplicate invoices.

Oblio as a stock source

The connection above issues invoices. Keeping easySales stock in step with Oblio's is a second, separate connection with its own credentials.

The Oblio stock source connection form under Stock sources, with Warehouse name, Vat ID, Token, Email and the warehouse name field.
The stock-source connection is separate, with its own copy of the same credentials.

Go to Integrations → Stock sources, press Connect on the Oblio card and fill in the same VAT ID, token and email, plus the warehouse the stock should be read from.

When Oblio refuses an invoice

The message comes back from Oblio unchanged and is shown on the order. Stock is by far the commonest reason.

What Oblio says What to do
Nu am putut descarca gestiunea pentru acest document. Produsele urmatoare nu au stoc suficient: Oblio's own stock is short for the products it names. Correct the stock in Oblio, or turn Use stock source off if you do not keep Oblio's warehouse up to date.
Produsul "…" nu are stoc suficient. The same thing for a single product.
Concurrent requests timeout. Please make one request at a time. Oblio received several requests for your account at once. Nothing is lost; the invoice can be issued again.
Too Many Requests, check back later Oblio's own rate limit for your account. It clears by itself.
The access token provided has expired Oblio ended the session earlier than expected. Issue the invoice again — easySales mints a new session token when the old one lapses.
Internal error. Please try again later. / an empty or 504 response Oblio did not answer. Nothing is wrong on your side; retry.
You are not allowed to use this API. The Oblio account does not have API access on its plan.
The company with cif … does not exist The Company registration number on the connection is not a company in that Oblio account.
Tipul produsului nu a fost gasit, tipul trebuie sa fie unul din: Marfa, Semifabricate, … A product exists in Oblio with a type Oblio will not invoice in this context. Fix the product type in Oblio.
Introdu o serie de document valida. This one is from easySales, not Oblio: the invoice series on the order does not exist in your Oblio account.
What Oblio's refusals mean

Credit notes, cancellations and payments

Action What happens in Oblio
Marking an order paid The invoice is collected in Oblio with the type from Payment type, or the one derived from the order's payment method. A Chitanta collection uses your Receipt series.
Returning an order easySales asks Oblio for a storno (credit note) against the original invoice.
Cancelling an invoice Oblio cancels the document; the number stays used, as it must.
Deleting an invoice Only possible while Oblio still allows it — otherwise cancel it instead.
What else the connection does

Frequently asked questions

The connection has Use stock source set to Yes, so every invoice also takes the goods out of Oblio's warehouse — and Oblio does not have enough stock for the products it lists. Either correct the stock in Oblio (and check that Warehouse name on the connection points at the right gestiune, exactly as Oblio spells it), or set Use stock source to No if you do not keep Oblio's warehouse up to date. This is the most common reason an Oblio invoice fails.

No. Oblio issues a separate API secret on its account settings page, and that is the token. The Username (Email) field takes the address the Oblio account is registered to. If the settings page has no token, your Oblio plan does not include API access.

That message is from easySales, and it means the series does not exist in your Oblio account. easySales sends the series configured on the marketplace or shop the order came from, and Oblio only accepts a series it already has. Create it in Oblio, or change the series in easySales to one Oblio knows.

No. easySales exchanges your email and token for a session token and renews it by itself when it lapses. If you see "The access token provided has expired" on an order, issue the invoice again — you do not need to touch the connection unless you changed the token in Oblio.

The name of the gestiune in Oblio, character for character — the field is case sensitive and the label says so. The same applies to Workstation name, which has to match an Oblio work point. Copy both out of Oblio rather than typing them.

Set Payment type to Chitanta under Show advanced options and fill in Receipt series on the connection with a receipt series that exists in Oblio. When easySales marks the order paid, the collection is recorded on that series. Leave Payment type empty and easySales picks the type from the order's payment method instead.

Turn on Enable idempotency key under Show advanced options. easySales then sends the order number with the invoice, and Oblio will not create a second document for a request it has already handled. The option is hidden if your account is deliberately set up to allow several invoices per order.

The first issues invoices. The second reads stock from Oblio into easySales, and it is a separate connection with its own VAT ID, token and email. They share nothing, so if you change the token in Oblio you have to update both.

Yes. Returning an order asks Oblio for a storno against the original invoice, so the credit note is created in Oblio with the same series rules as the invoice.

Because Invoice language under Show advanced options is set, and it applies to every invoice. Clear it and easySales uses the language of the shop or marketplace the order came from, provided Oblio supports that language.

Was this guide helpful?