BeryX · E-commerce and retail
Dashboard revenue doesn't match the bank. Again.
Orders from several channels, coupons, refunds, addresses and a catalogue that changes every hour. When one of these breaks, it breaks silently — until month-end. BeryX watches them for you.
Free account, no card. The demo opens with data from a Portuguese online store.
The pain
Every new channel is one more data source nobody owns.
You're not short of dashboards. Nobody knows whether what's on them is true.
Inflated revenue
Payment gateway retries duplicate orders; refunds come in as negative totals. The number that goes to the board is wrong and nobody knows why.
Returned parcels
Emails without an @, postcodes without the hyphen, country spelled out: confirmations don't arrive, shipping is miscalculated and the carrier sends the parcel back.
Promotions that lose money
A coupon set up as a percentage instead of euros means negative margin on every order — and you only find out at reconciliation.
Connectors that stop without an alarm
The marketplace stops syncing on a Friday. The dashboard stays green, just with three-day-old data.
How BeryX fixes it
Ready-made retail rules, freshness alerts and the fix in SQL.
E-commerce rule pack
order_id uniqueness, non-negative totals, discounts between 0 and 100%, email format, PT postcode and ISO country — applied in one click.
Freshness per table
BeryX learns each source's rhythm and warns you when orders stop arriving, before the weekly close.
Duplicates and anomalies
Detects duplicate rows and volume or distribution drift without you writing a rule.
Proposed fix
For each issue, the AI agent suggests the likely cause and the SQL to fix it — with estimated risk. You decide; BeryX never writes to your source.
Proof, not mockups
BeryX running on the «Online store» demo workspace.
Real screenshots of the app, taken on the vertical's seed pack: fictional but plausible data, generated deterministically, with 8 planted issues — each with the backstory of the incident that caused it. The industry rule pack comes already applied, so the first scan flags exactly these issues. It's what you see when you open the demo.
What the first scan catches
8 issues, 8 stories you've seen happen.
- 01
Invalid sign-up emails
clientes.emailMobile checkout v2.3 (released in May) stopped validating emails — 4% of sign-ups have commas, spaces or a missing @, and confirmation emails never arrive.
- 02
Country spelled out
clientes.paisThe marketplace import stored «Portugal» instead of the ISO code «PT» — per-country shipping costs fail for those customers.
- 03
Postcodes without the hyphen
clientes.codigo_postalThe old address form accepted «1000100» — the postal service returns those parcels as undeliverable.
- 04
Duplicate orders
encomendas.order_idOn Black Friday, the payment gateway retry stored 14 orders twice — the sales dashboard inflated the day's revenue.
- 05
Refunds as negative totals
encomendas.totalCustomer support logged refunds as orders with a negative total instead of credit notes.
- 06
A 110% discount
encomendas.desconto_pctThe «VOLTA10» coupon was set up as a percentage instead of euros: 3 orders went out with a 110% discount.
- 07
Orders stalled for 3 days
encomendas.data_encomendaThe marketplace connector stopped syncing on Friday — nobody noticed until the weekly close.
- 08
Lines with zero quantity
linhas_encomenda.quantidadeChristmas campaign freebies were entered as lines with quantity 0, skewing stock turnover.
fictional data
Other industries
See your online store through BeryX's eyes.
Open the demo with the online store data and walk through the eight planted issues — or connect your own source, read-only, in minutes.