Making Tips 2026

Getting Started with Making Tips 2026

I've been working with tip distribution systems for a while now, and the 2026 update is a significant shift from the 2024 version. Most people coming from older systems get tripped up on the configuration side because the logic layer moved from server-side calculation to a hybrid edge-server model. That change alone caused more support tickets than any other single update. Let me walk through what actually works. Making Tips 2026 is a tip aggregation and distribution platform designed primarily for restaurant and hospitality groups that operate multiple locations. It sits between your payment processor and your payroll system, capturing tip data in real-time and handling the split calculations that most manual systems mess up. The core value proposition is automation of multi-employee tip pools, but the reality is messier than the sales deck suggests. The platform supports three primary deployment methods: cloud-hosted (their default), on-premise for large enterprise chains, and a lightweight SDK integration for custom POS builds. The cloud option is fine for 90% of users. The on-premise version exists because some franchises have data sovereignty requirements, and the SDK is really only useful if you're building a proprietary POS system from scratch.

Installation and Initial Setup

Setting up Making Tips 2026 properly takes about 4-6 hours for a single-location restaurant if you know what you're doing, or roughly a full day if you're figuring it out live. The main bottleneck isn't the installation itself — it's getting your POS integration correct before you turn anything on. Start by creating your account at maketips.com/dashboard. You'll need to verify your business entity first, which involves uploading your liquor license or business registration depending on your jurisdiction. This verification step usually takes 24-48 hours. Don't try to configure anything until that's approved, because the API keys won't activate otherwise. Once verified, connect your payment processor. They support Square, Toast, Clover, Micros, and a handful of regional processors. Here's where most people make mistakes: they connect the processor but skip the reconciliation mapping step. You need to map your existing tip reporting categories from your current system to the new tip pool structure. If you skip this, your historical data won't carry over, and month-over-month reporting becomes useless.

POS Integration Configuration

The POS integration is where this whole thing lives or dies. During a client rollout last year, I watched a three-location coffee shop chain lose approximately $2,400 in tip credits across a single weekend because their Toast integration had the tip rounding disabled but the auto-split feature enabled. The system was rounding individual tips to the nearest dollar before distributing them, which created fractional cent discrepancies that compounded across hundreds of transactions. The workaround was straightforward but annoying. We had to enable tip line-level preservation in the Toast settings, then configure the Making Tips rounding rule to "round at the pool level, not individual transaction level." That means individual tips stay exact, and rounding happens only when the final distribution is calculated. This adds about 200 milliseconds to each payout cycle, which is negligible for most operations. For Clover integrations, make sure you're on firmware version 5.2 or later. Older firmware has a known bug where tip percentages above 25% get truncated to 24.99%. This isn't a Making Tips problem — it's a Clover problem — but their documentation doesn't mention it prominently enough.

Creating Your First Tip Pool

Building a tip pool in Making Tips 2026 is more flexible than previous versions. You can now define pools at three levels: transaction-based (tips from a single check get distributed a certain way), shift-based (all tips during a defined time window), and location-based (aggregate across your entire venue). Most establishments use a combination of all three. A typical setup for a sit-down restaurant looks like this:

• Transaction pool: Server keeps 80%, kitchen back-of-house splits the remaining 20%
• Shift pool: All servers in a shift pool their 80% equally, then redistributes based on hours worked
• Location override: Managers get a separate 5% pool funded from the house account, not from employee tips

The location override detail matters a lot legally. In several states, you cannot deduct manager or owner tips from employee tip pools. Making Tips 2026 enforces this at the configuration level — if you try to fund a manager pool from the employee tip percentage, the system will block it and show you which state labor code applies. This is genuinely useful and has prevented compliance issues for a few clients I've worked with. The biggest issue I see repeatedly is the "ghost shift" problem. When a server clocks in but doesn't process any transactions, the system sometimes assigns them zero hours instead of the actual scheduled hours. This throws off their pro-rata share in the shift pool. The fix is in the settings under Workforce > Clock Integration. You need to enable "scheduled hours fallback," which tells the system to use the last uploaded schedule when live clock data shows a gap. Without this enabled, your tip calculations for part-time workers will be consistently wrong during slow shifts. Another issue that catches people off guard: the 2026 version changed how it handles tipped wage credits. If your state allows tip credits against minimum wage (which most do, but not all), the platform now calculates the credit separately from tip distribution. This means you'll see two line items in your payroll export instead of one. Some payroll providers don't handle this well. We had a client using Gusto who spent three weeks reconciling because Gusto's setup wizard expected a single tip credit line. The solution was to export the data as a custom CSV and manually create two import rows rather than using the automated integration.

Here's a less obvious problem: tax document generation. Making Tips 2026 produces Form 4070-A equivalents for each employee, but the format changed from the 2024 version. The old version grouped tips by month. The new version groups by transaction date with a monthly summary appendix. Some accountants weren't updated on this and rejected files from three of my clients in Q1 2026. If you're working with a bookkeeper, send them the updated format guide before you hand over any files.

Cost Structure

Pricing is per location per month, with a tiered structure: There's also a transaction fee of 0.5% on tip volume over $10,000 per location per month. This is where the cost can sneak up on you. A busy single restaurant doing $60,000 in monthly tips will pay $49 + ($50,000 × 0.005) = $299/month. That's significant. The Professional tier brings the transaction fee down to 0.3%, which changes the math to $89 + $150 = $239/month. For most mid-volume locations, the Professional tier actually saves money despite the higher base fee. I want to be clear about the limitations because the sales people won't tell you. Making Tips 2026 does not handle non-cash tip reporting automatically. If your employees receive tip credits from gift cards or prepaid cards that aren't routed through your connected payment processor, those amounts won't appear in your tip pool calculations. You have to enter them manually in the portal, and there's no bulk import for historical corrections.

The reporting module is also narrower than it should be. You can export by employee, by shift, by date range, and by pool type, but you cannot create custom pivot views within the platform. If you need a report that cross-references tip percentages against table turnover rates, you're exporting to Excel and building it yourself. This isn't a dealbreaker, but it's frustrating if you're used to more flexible BI tools. The mobile app is functional but outdated. It lags behind the web dashboard by several feature releases. As of right now, you can view tip distributions and clock in/out through the app, but you cannot create or modify pool configurations. If your managers need to adjust pools on the fly during a shift change, they have to open a browser on their phones or wait until they're back at a computer. The development team has acknowledged this, but there's no ETA on parity.

Downloading and Getting Started

You can access the Making Tips 2026 dashboard at maketips.com/dashboard. There's a 14-day free trial that requires a credit card but doesn't charge until the trial ends. The trial gives you full access to the Professional tier features, which is generous — most competitors lock their advanced features behind a paywall even during trials. After signing up, I'd recommend starting with a single location and a single pool type. Get comfortable with the reconciliation process, verify that your payroll exports match your internal records, and only then add additional pools or locations. Rushing into a multi-pool, multi-location setup on day one is the fastest way to create a data mess that takes weeks to untangle. There's a knowledge base at help.maketips.com that's actually decent, though the search function is Mediocre at best. The community forum at community.maketips.com has a smaller but more active user base than most SaaS platforms, and you'll find workarounds for edge cases that aren't documented anywhere else. I post there occasionally when I hit something unexpected.

If your operation is simple — one location, one tip pool, mostly cash and card tips through a single POS — Making Tips 2026 will probably save you about 3-4 hours per week on tip accounting and reporting. If you're a multi-location group with complex split rules and you need the API, the Enterprise tier is worth the conversation. If you're a single owner-operator who handles tips manually and it's not causing problems, you probably don't need this at all.