Magento 2 Tips & Service Charge Management

Magento core has no concept of tips or service charges. They are not a product, a tax, or a discount — they need their own data model, totals collector, and payout reporting. We deliver a proper module under app/code/Ecosire/TipsServiceCharge that adds both as first-class totals.

At online checkout, a custom total collector (registered in etc/sales.xml and exposed through the checkout LayoutProcessor) adds a configurable tip prompt — percentage presets or a fixed custom amount — plus a percentage or fixed service charge with correct tax handling driven by your store's tax class rules. Values persist on the quote and order via extension attributes and extension_attributes.xml, so they survive into invoices, credit memos, and the order grid.

At POS (Magento POS, Adobe Commerce POS, or your connected terminal flow), a plugin/interceptor on the payment capture path injects a tip prompt for both card and cash tenders, writing the tip back to the same order totals.

Pooling and splitting is handled by a service-contract-backed engine: define pool groups, weighting rules (hours, role, equal split), and per-staff attribution. A cron job aggregates tips per pay period into a payout report, exposed in the admin grid behind a dedicated ACL resource and available over REST and GraphQL for payroll export.

Everything is delivered as clean, upgrade-safe code — di.xml wiring, plugins and observers instead of core edits — so it survives Magento and Adobe Commerce upgrades. ECOSIRE handles the build, installation, configuration of your tip and charge rules, and ongoing support.