feat(acuamania-brou) · bfdfe8bcbuiltA coupon cannot be stacked with the bank benefit
If there is a coupon in the cart, BROU Recompensa is blocked. A second fix covers virtual coupons, which have no entry in the database.
acuamania.uy sells its tickets on WooCommerce. Every purchase is charged through Plexo, gets its electronic invoice and reaches the customer as a QR ticket that is validated at the gate.

Acuamanía, water park in Uruguay
Developer at DeepZide, alongside two other devs
BROU benefit plugin, fixes to the e-invoicing plugin (built by another team), checkout, performance and Docker
Local, staging on Coolify and production on Docker
The park sells almost everything online and in season. A purchase does not end at payment: it has to go through the local gateway, the invoicing required by law and the park gate, without the customer noticing any of it.
If one piece fails, the problem shows up in the entrance queue, with the customer standing right there.
Uruguayan cards through Plexo, the gateway the country's banks use.
Every paid order issues its electronic tax receipt. Every refund, its credit note.
Partner deals and BROU Recompensa, the Banco República benefit that depends on the card used to pay.
One QR ticket per person, which staff validate in seconds from a phone.
Five steps the customer experiences as one. Scroll down and watch them in order.
The checkout separates final consumers from companies, and validates the data each invoice requires. Partner deals are applied here. If the card is from BROU (the BIN says so, its first digits), the order enters BROU Recompensa without touching the prices.
The local gateway charges the card. BROU Recompensa payments are routed to the BROU merchant and the rest to the general merchant, so each one settles separately.
Once the payment is confirmed, an invoice plugin (built by another team) requests the tax receipt from Gsoft and stores it on the order, with its fiscal QR. A refund generates the credit note. Every attempt is kept in a log inside the admin, so a failure can be found without opening the server.
FooEvents issues one PDF ticket per person, each with its own QR, and the customer receives it by email along with the order.
Staff scan with the check-in app, which talks to the FooEvents API. A mu-plugin loads only what is essential on those calls, so validation does not wait for the rest of the site.
routing diagram · no real data
illustrative · no real data
Six cases taken from my commits on this project. Each card carries the commit that solved it.
feat(acuamania-brou) · bfdfe8bcbuiltIf there is a coupon in the cart, BROU Recompensa is blocked. A second fix covers virtual coupons, which have no entry in the database.
feat(acuamania-brou) · 6bbf816bbuiltThe plugin accepts 6- and 8-digit BINs and compares the first 6, so no BROU card is left without the benefit.
fix(efactura) · 7c4063eeimprovedIf the customer's document fails the check digit, the invoice is issued without it instead of failing. The recipient data goes in the XML that Gsoft accepts.
feat(checkout) · 9fedfb40improvedThe payment block stays closed until the billing details are complete, and the fields unlock in order.
perf(fooevents) · 6ea4cadfbuiltOn the check-in app's REST calls only WooCommerce and FooEvents are loaded, and validation responds sooner.
feat(emails) · be9c558dimprovedOrders that expire unpaid no longer notify as cancelled, and the inbox only receives what matters.
Where an order goes
Every change goes through staging before reaching the live store. Production is updated by hand and always with a database backup first.
Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.