The Role of WooCommerce
MIDDAG Account and WooCommerce work as two complementary layers. WooCommerce is the commerce engine -- it handles products, pricing, cart, checkout, payments, shipping, and tax. MIDDAG Account is the lifecycle engine -- it handles organizations, entitlements, licenses, contracts, services, renewals, and policies.
Neither system replaces the other. They each own a distinct set of responsibilities.
What WooCommerce handles
| Responsibility | Details |
|---|---|
| Product catalog | Product names, descriptions, images, pricing, variations, categories |
| Cart and checkout | Not customer-facing -- orders are created by the admin, quotes, or automation |
| Payment processing | Stripe (credit card), Banco Inter (Pix, Boleto) via gateway plugins |
| Subscriptions | Recurring billing, proration, upgrade/downgrade, retry via WC Subscriptions |
| Tax calculation | Tax rates, tax classes, automatic tax calculation |
| Shipping | Shipping methods and zones (rarely used -- most products are digital) |
| Coupons | Discount codes, percentage or fixed discounts |
| Order storage | Order records stored in HPOS (High-Performance Order Storage) |
What MIDDAG Account handles
| Responsibility | Details |
|---|---|
| Organizations | Customer accounts, collaborators, tax IDs, billing entity |
| Entitlements | What the customer has access to, with class, status, and expiration |
| Licenses | License keys, activation limits, downloads (PLG class) |
| Environments | Managed hosting instances (ENV class) |
| Services/Contracts | Ongoing service agreements, credit balances (SVC class) |
| Policy engine | Renewal, refund, cancellation, payment recovery, SLA rules |
| Dual-entity routing | Routing transactions to MIDDAG BR or MIDDAG GLOBAL based on customer data |
| Invoice sync | Syncing Stripe invoices to the local domain, linking to orders and entitlements |
| Tax invoices (NFSe) | Brazilian tax invoice issuance via ISSNet (BR entity only) |
The boundary
The link between the two systems is the product mapping. Each WooCommerce product carries a meta field (_middag_entitlement_class) that tells MIDDAG Account what kind of entitlement to create when a customer purchases it.
When to configure in WooCommerce
- Creating or editing products (name, price, description, images)
- Setting up payment gateways (Stripe, Banco Inter)
- Configuring tax rates and tax classes
- Managing coupons and discounts
- Reviewing order details and payment status
- Handling subscription settings (billing intervals, retry schedules)
When to configure in MIDDAG Account
- Mapping products to entitlement classes
- Setting policy overrides (renewal, refund, cancellation, SLA)
- Managing organizations and their collaborators
- Reviewing entitlement status and lifecycle
- Configuring dual-entity routing rules
- Setting up notification templates and timing
- Managing license keys and environment provisioning
WooCommerce is invisible to customers
Customers never interact with WooCommerce directly. The customer portal uses MIDDAG Account terminology -- "orders" and "invoices," not "WooCommerce orders." The checkout is not a traditional WooCommerce storefront. Orders are created through quotes, admin actions, or automation, and customers pay through the portal.
WooCommerce admin pages are used exclusively by your operations team in the WordPress back office.
Satellite plugins
Two additional WooCommerce plugins extend the commerce layer:
| Plugin | Purpose | Relationship to MIDDAG Account |
|---|---|---|
woocommerce-banco-inter | Banco Inter payment gateway (Pix, Boleto) | Integrates via standard WC payment hooks |
woocommerce-quotes | Quote entity in WooCommerce | MIDDAG Account consumes via hooks and API |
Both are maintained by MIDDAG and integrate through WooCommerce hooks -- never through direct code coupling.
Related pages
- Products and Entitlement Classes -- how products map to entitlement classes
- Orders and Entitlements -- the order-to-entitlement pipeline
- Connect WooCommerce -- initial setup guide
- Orders -- order concept reference