Magento 2 Tips & Service Charge Management

Key Features

Tip prompt at online checkout with percentage presets or a fixed custom amount, rendered via the checkout LayoutProcessor and a custom KnockoutJS component

Custom totals collector registered in etc/sales.xml so tips and service charges become first-class order totals (not fake products or discounts)

Percentage or fixed service charge with correct tax-class handling, configurable as tax-inclusive or tax-exclusive

POS tip capture via a payment-path plugin/interceptor for both card and cash tenders, writing back to the same order totals

Tip pooling with configurable pool groups and weighting rules (equal split, hours-weighted, or role-weighted) behind a service contract

Per-staff tip attribution stored against the order and surfaced in dedicated admin reporting grids

Persistence across the order lifecycle via extension_attributes.xml so tips/charges flow into invoices, credit memos and the sales order grid

Cron-driven payout aggregation per pay period producing exportable staff payout reports

REST and GraphQL endpoints for tips, service charges and payout summaries for payroll/POS integration

Admin configuration under Stores > Configuration with a dedicated ACL resource gating tip rules, pool setup and payout reports

Refund-aware logic that adjusts tip and service charge totals on credit memos and partial refunds

Multi-store / multi-website scope support so different venues can run different tip presets and charge rates

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

This is a build-to-order Magento 2 / Adobe Commerce extension, not an instant Adobe Commerce Marketplace download. ECOSIRE builds it to your store's exact gratuity rules, installs it on your environment, and supports it after go-live.

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.

What you get

Custom Magento 2 module Ecosire_TipsServiceCharge delivered under app/code (or as a Composer package) with di.xml, sales.xml, ACL and full source

Database schema (declarative schema db_schema.xml) plus extension attributes for tips, service charges, pool groups and per-staff attribution

Checkout and POS integration: totals collector, LayoutProcessor checkout component, and payment-path plugin for card and cash tip capture

Pooling and split engine with admin configuration for pool groups, weighting rules and pay-period payout reports

REST and GraphQL API endpoints with schema and example payloads for payroll/POS export

Installation and configuration on your environment (Open Source or Adobe Commerce), including bin/magento setup:upgrade and cache/index validation

Documentation: admin user guide for tip rules and pooling, plus a technical README covering module structure and upgrade notes

Post-launch support window with bug fixes and a compatibility check against your next Magento/Adobe Commerce upgrade

Who this is for

Multi-location restaurant operator

Runs several venues on one Magento/Adobe Commerce instance and needs each location to set its own tip presets and service charge rate, with pooled tips split fairly across staff per pay period.

Hospitality finance / payroll manager

Needs accurate per-staff tip attribution and pay-period payout reports that export cleanly to payroll, with service charges taxed correctly and reconciled against invoices and refunds.

Magento agency or in-house dev lead

Wants tips and service charges implemented as upgrade-safe totals collectors, plugins and service contracts — not core hacks — with REST/GraphQL endpoints they can wire into existing POS and payroll systems.

How Magento 2 Tips & Service Charge Management Compares

Criterion	ECOSIRE	Custom Build	Competitor
Tips as a first-class order total (not a fake product or discount)	Included	Partial support	Partial support
Service charge with correct tax-class handling	Included	Partial support	Partial support
POS tip capture for both card and cash tenders	Included	Partial support	Not included
Tip pooling, split rules and per-staff attribution	Included	Partial support	Not included
Cron-driven pay-period payout reporting with REST/GraphQL export	Included	Partial support	Not included
Built, installed and supported for you on your environment	Included	Not included	Not included
Upgrade-safe (plugins/observers/service contracts, no core edits)	Included	Partial support	Partial support
Tailored to your exact venue tip rules and weighting	Included	Included	Not included

Frequently Asked Questions about Magento 2 Tips & Service Charge Management

Is this an instant download from the Adobe Commerce Marketplace?

No. This is a build-to-order extension. ECOSIRE builds it to your specific tip and service charge rules, installs it on your Magento Open Source or Adobe Commerce environment, and supports it. You are not buying a generic Marketplace package — you are buying a module tailored to your venues and payout logic.

How long does delivery take?

Typical lead time is about 2 to 4 weeks from confirmation of requirements, depending on the complexity of your pooling rules, POS integration and number of stores. After a short scoping call we confirm an exact timeline before any build work starts. Installation on your environment is included.

What support and updates are included after delivery?

Every build includes a post-launch support window covering bug fixes and configuration help. Because the module is written with plugins, observers and service contracts instead of core edits, it is upgrade-safe; we also include a compatibility check against your next Magento or Adobe Commerce upgrade. Extended support and feature work are available as an ongoing arrangement.

Does it work with both Magento Open Source and Adobe Commerce?

Yes. The core module runs on both. Adobe Commerce-specific touchpoints (such as B2B, advanced staging of charge rates, or Adobe Commerce POS hooks) are wired in when your edition supports them. We confirm your edition and version during scoping and build accordingly.

How are tips captured at the POS for cash payments?

A plugin/interceptor on the payment capture path adds a tip prompt for both card and cash tenders. The captured tip is written back to the same order totals used at online checkout, so pooling, attribution and payout reporting treat POS and online tips identically.