The pages the law requires on every website that sells
What's mandatory, what's recommended and what's an urban legend — plus what actually has to be inside each page.
3 min readWhen you need a cash register, what SUPTO means, what Annex 38 demands — and how not to be fined over a file encoding.
This topic throws more people into a panic than anything else in e-commerce. The panic is usually disproportionate to the actual work — but the gaps really do get fined, so let's lay it out.
This is a plain-language explainer, not tax advice. For your specific case, ask your accountant — they cost less than one penalty.
If you sell goods or services through a website, in Bulgaria it must be declared to the revenue agency (NAP). This is a separate step from registering the company and from VAT registration.
In practice you submit information about the online store — domain, type of activity, where the data is hosted, what software you use. It's filed electronically with a qualified electronic signature.
If you change platform or domain, the details must be updated. That's the part people most often forget.
The answer depends entirely on how the money arrives.
You usually do NOT need a fiscal device if:
You usually DO need one if:
The logic is simple: the state wants a trace for every cash payment. When the money passes through a bank or a courier, the trace already exists.
If you sell both online and in person, the in-person rules apply to those payments.
SUPTO stands for "software for managing sales in a commercial establishment". The definition is broader than it sounds: software that processes sales information and manages the sales process.
If your software falls under the definition, extra requirements follow — including that it be declared, keep an audit log, and not allow sales data to be deleted.
Two nuances save a lot of nerves here:
Pinning this down exactly is an accountant's job — but it's worth asking before you pick a platform, not a year later.
If you're covered, the revenue agency can demand a standardised audit file of your sales data. The format is described in Annex 38 and it is very specific:
A file with the wrong encoding or a misplaced element is rejected as if you'd submitted nothing. And that is where penalties come from — a format error rather than hidden income, which is particularly galling.
If you're on Brandolog, NAPpy generates the file for you: it reads your sales, produces validated XML in the correct encoding, and hands it over ready to submit. On another platform, ask your provider whether they can export per Annex 38 — an answer of "we can give you a CSV" means no.
Briefly, so we don't drift:
In detail and in plain language: VAT, invoices and registration.
For a new shop taking cash on delivery and bank payments:
That's it. It isn't a six-month project and it isn't a reason not to launch. It's a list you walk through once — then update when something changes.
Written by
The Brandolog team
We write down what we learned building Brandolog — and watching thousands of people ship their very first website.
What's mandatory, what's recommended and what's an urban legend — plus what actually has to be inside each page.
3 min readWhen VAT registration kicks in, when you must issue an invoice, and why voluntary registration is sometimes profitable and sometimes a mistake.
3 min readA composite portrait from the dozens of shops we've watched launch: the numbers, the panics, and the month something clicks.
4 min readSnap a website together out of blocks in minutes — free, no code, no sign-up to begin with.