Croatian WordPress hosting for order history in two currencies.
Croatia adopted the euro recently, which means any store older than that has orders recorded in kuna sitting alongside orders in euro.
History in a currency that is gone.
A changeover does not rewrite the past, and every report crossing that date has to handle two units.
Old orders keep their original currency
Rewriting historical totals into euro destroys the record of what was actually charged. Orders retain the currency they were placed in, with the conversion stored rather than substituted.
Reports that cross the changeover
A twelve-month comparison spanning the switch is adding two units together. Reporting converts at the recorded rate instead of treating the numbers as interchangeable.
Invoices reproducible as issued
A reissued invoice has to show what the customer paid, in the currency they paid it. That is a retention requirement rather than a display preference.
EU origin and EU backups
Storage stays in the EU with the location named, which matters for a market that recently joined the euro area.
Seasonal traffic on a tourism scale
Coastal and accommodation sites run several times their winter baseline through summer, which is planned for rather than discovered.
Two units in one ledger.
The failure is a revenue chart that looks like a collapse or a boom at the changeover date, because two currencies were summed as if they were one.
- Historical orders retain their original currency
- Reports convert at the recorded rate
- Invoices reproducible as originally issued
- Summer capacity planned for
A ledger that still reconciles.
Speed is not the issue on a Croatian store. Whether a report spanning the changeover produces a number anybody can defend is.
What we change for Croatian stores
A recent currency changeover leaves a permanent seam in the data, and every report crossing it has to account for that.
| Setting | What we do | Why |
|---|---|---|
| Historical currency | Original currency retained on legacy orders | Rewriting past totals into euro destroys the record of what was actually charged, which is the thing an invoice has to reproduce. |
| Report conversion | Applied at the recorded rate rather than summing units | A chart spanning the changeover adds kuna to euro unless conversion is explicit, producing a discontinuity that looks like a trading event. |
| Invoice reproduction | Reissued showing the currency the customer paid | Retention obligations require reproducing the document as issued, not a restated version in today's currency. |
| Storage disclosure | EU location named for site and backups | Recent accession makes buyers here more likely to ask precisely rather than accept a region name. |
| Seasonal capacity | Planned around a summer peak well above baseline | Coastal and accommodation sites have a genuine season, so an annual average understates the load for months at a time. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Should I convert old kuna orders to euro?
Why does my revenue chart jump at the changeover?
Can I reissue an old invoice?
How should I plan for summer?
Keep the ledger defensible.
Move the store to an EU origin - migration is free, order history intact.