Blazo Checkout

Seven in ten shoppers who reach checkout leave without buying. That’s not a traffic problem — it’s a checkout problem. Blazo Checkout replaces your WooCommerce checkout with a hosted one built to close the sale, win back the ones who almost didn’t, and sell them a little more on the way out.

Here’s what changes the day you install it:

Fewer carts die at checkout

A faster, cleaner, trust-built checkout page — guest-first, mobile-tuned, no surprise costs at the last step. Every field on it exists because it earns its place.

Built for speed, not just for looks

Your branding and settings load from the edge network first, falling back to the API only if needed. Cities and delivery offices load from the API first, falling back to the edge if it’s slow. Order completion tries the API first, then the edge network as a backup. Every step has a fallback, so shoppers never wait on a single point of failure.

It stays up even when your site doesn’t

If your store goes down mid-checkout, the order isn’t lost — Blazo holds it and pushes it into WooCommerce the second your site is back. And if your courier’s API goes down (it happens more than anyone admits — cities and pickup offices just vanish from checkout, and the sale goes with them), Blazo already has that data cached on its own servers. Your checkout keeps working. Your customer never finds out there was a problem.

Abandoned carts come back to life — on every channel

Someone bails before paying? Blazo follows up by email, SMS, Viber, Telegram, WhatsApp, or a phone call — whichever gets a real human to finish the order. Revenue you were already writing off as lost.

Every order gets bigger

Order bumps at checkout and post-purchase offers, placed exactly where shoppers are most willing to say yes. (Post-purchase upsells: coming soon.)

A thank-you page that keeps working after the sale

Order summary, delivery status, tracking, “contact support” — all one click away, right after purchase. Fewer “where’s my order” tickets, more customers who trust you enough to come back.

You see the money, not just the orders

A dashboard built around one number: how much Blazo actually made you — recovered carts, upsells, and the conversion lift, broken out and dated. No spreadsheets, no guessing.

Test what actually converts

Run steps vs. one-page checkout head-to-head and let the data decide. More test types are coming.

Make it look and behave like your checkout

Style it to match your brand, and set exactly which fields are required and which aren’t. Field hide/reorder controls are coming next.

Know which orders are actually going to ship

Every customer gets a risk score — critical wherever cash-on-delivery is the default payment method, because a refused COD parcel means you pay courier fees both ways for nothing.

Sell printed and digital side by side

Selling a book as both print and e-book? Shoppers switch between the versions right in the checkout with one click — no trip back to the product page. Digital products (virtual or downloadable in WooCommerce) are recognised automatically: cash on delivery is hidden for them, and an order with only digital items skips the delivery step entirely — no courier, no shipping charge, no address to type.

Built for real-world delivery, wherever you sell

Courier selection, pickup-office lookup, cash-on-delivery, B2B company/EIK fields — the messy logistics details that lose sales when a generic checkout gets them wrong. Deep support for Central & Eastern European delivery out of the box.

Make it yours, top to bottom

Run checkout on your own custom domain. Every word on the page is translatable, so shoppers never feel like they left your store.

Your order statuses, everywhere they matter

The custom statuses you define in Blazo show up in WooCommerce with the right name — in the admin, and on the customer’s My Account > Orders screen too. They keep their names even if the API is unreachable, and they appear in your admin language. Create a waybill and the order moves to the status you mapped instantly, right there on the order screen. Once an order is with the courier it’s locked from editing, so line items can’t drift away from the waybill already printed.

Set up once, never touch again

Connect with a single onboarding token. No copying API keys or secrets by hand. Your custom order statuses sync automatically. Every order lands back in WooCommerce — customer, address, shipping, fees, all of it — the moment it’s confirmed.

Bank-grade by default

Every checkout payload is AES-256-GCM encrypted and HMAC-signed. Every confirmation is signature-verified, replay-protected, and de-duplicated. Order totals are checked against what the shopper actually confirmed, so price tampering gets caught, not shipped.

Coming soon

In-house heatmap tracking, so you see exactly how shoppers move through your checkout — no third-party script required. And a dedicated order-tracking page with its own upsell placements, so the sale doesn’t stop at “thank you.”

Full feature list

• Hosted checkout that replaces native WooCommerce checkout — redirect and done.
• Edge-first loading with automatic API fallback for branding, delivery data, and order completion.
• Offline resilience: orders and courier data are held and synced automatically if your site or your courier’s API goes down.
• Abandoned cart recovery via email, SMS, Viber, Telegram, WhatsApp, or phone call.
• Order bumps at checkout (post-purchase upsells coming soon).
• Branded post-purchase thank-you page with order status, tracking, and support links.
• Revenue dashboard: recovered revenue, upsell revenue, conversion lift, all in one view.
• A/B testing between step and one-page checkout (more test types coming).
• Custom styling, with control over which fields are required.
• Per-customer risk scoring, purpose-built for cash-on-delivery markets.
• Courier + pickup office selection, cash-on-delivery, B2B company/EIK fields.
• Custom checkout domain support.
• Fully translatable checkout.
• Custom order status sync from Blazo into WooCommerce — localised names, shown on the customer’s My Account screen as well as in the admin, and kept through API outages.
• Waybill creation moves the order to its mapped status immediately, on the order screen.
• Orders in a Blazo custom status are locked from editing, so line items can’t diverge from a printed waybill.
• Waybill number shown prominently on the order screen with one-click copy.
• Zero-touch onboarding via one-time token.
• AES-256-GCM encryption + HMAC signing on every payload.
• HMAC-verified, replay-protected, idempotent order confirmation.
• Order-total tampering detection.
• High-Performance Order Storage (HPOS) compatible.
• Configurable order status mapping: which status new orders get (by delivery and payment method), which status each event pushes, and how WooCommerce statuses map back.
• Coming soon: in-house heatmap tracking, and a dedicated order-tracking page with upsell placements.

A Blazo account is required. This plugin is the connector — the checkout itself, the recovery engine, and the dashboard live on Blazo’s platform.

External services

This plugin relies on the Blazo Checkout third-party service to function. It is not usable without a Blazo account, and by installing it you direct your store’s checkout traffic to Blazo.

What is sent, and when

1. At checkout (browser redirect). When a shopper clicks “Proceed to checkout”, the plugin builds an order payload and redirects the shopper’s browser to your configured Blazo checkout URL. The payload is AES-256-GCM encrypted and HMAC-signed and contains: store ID, currency, return/callback URLs, cart line items (product name, SKU, price, quantity, image URL, variation data), order totals, and the customer’s email, first name and last name and, if they are logged in, their WordPress user ID (where available). Each line also carries its category IDs, brand, whether the product is virtual, downloadable or needs shipping, and cart-item keys so bundled items stay linked to their bundle. When the shopper comes from the instalment calculator on a product page, it also carries the chosen PB Personal Finance programme and down payment.

2. On connection (server to server). When the merchant connects the store, the plugin sends a one-time onboarding token and the site URL to the Blazo API (/plugin/bootstrap) to retrieve the store configuration.

3. Order confirmation (server to server). Blazo calls back to this site to create the order. No store-initiated PII is sent in this step; the plugin receives and verifies the confirmed order data. If your site is unreachable when Blazo tries to deliver an order, Blazo holds it and retries automatically once your site is back up.

4. Status sync (server to server). The plugin periodically requests your custom order-status definitions from the Blazo API.

5. Customer accounts (server to server, from Blazo to your site). When a shopper logs in or creates an account in Blazo Checkout, Blazo sends their email address (and, for a login, the password they typed) to signed endpoints on your site. The password is checked by WordPress and is never stored by Blazo. Your site answers with the customer’s ID, name, email, phone and saved billing and shipping addresses so the checkout can be prefilled. Only when the matching WooCommerce “Accounts & Privacy” settings are enabled.

6. Instalment offers on product pages (server to server). On single product pages of stores that offer PB Personal Finance credit through Blazo, your site asks the Blazo API (/plugin/bnp/widget) for the bank’s instalment offers. It sends the store ID, product ID, variation ID, quantity, price, down payment and the product’s category IDs. No shopper data is sent. Answers are cached on your site for a few minutes.

Service endpoints

• Checkout URL — configured by the merchant (e.g. https://checkout.blazo.bg, or your own custom domain)
• API base URL — configured by the merchant (e.g. https://api.blazo.bg)

Service provider, terms and privacy

• Service provided by Blazo (a product of Fantasy Software Ltd) — https://blazo.bg
• Terms of Service — https://blazo.bg/terms
• Privacy Policy — https://blazo.bg/privacy

Merchants are responsible for disclosing this data flow to their own customers as required by applicable privacy law.