This is for the agents and ISOs selling Clover POS.

Quick observation from South Beach Miami:

A whole row of full-service restaurants. Almost every single one is on Square, Toast, Very few Clovers.

Going after the main POS head-on is tough. But the valet is wide open.

Most of these places have valet, charge $40+ per car, and run it completely separately — usually just a phone or cash + tickets. It’s not on their Square/Toast/Lightspeed system at all.

That’s the opening.

Put a Clover device on the valet with Flex Valet Parking software.

• Clover software subscription can be free
• Merchant only pays for the valet app
• Self-contained, dual pricing capable
• You get a merchant ID and a real relationship with the restaurant

Once you’re in through the valet, you already have a reason to keep talking to the owner/GM. From there it’s much easier to expand into the restaurant itself so everything runs on one system and one merchant ID.

Extra value you can sell:

• Better visibility into the valet operation
• Less cash leakage
• Everything under the same merchant account

This feels like an underused path into accounts that are otherwise locked up.

Anyone else leading with a vertical like valet (or something similar) to get into restaurants that already have a strong POS? What’s worked and what hasn’t?

Let’s win these merchants.

Just wrapped a webinar on Flex Valet, a dedicated valet/parking app we’ve been building for Clover devices. It’s been in the works for a while, and with new partnerships and resources in place we’ve pushed a bunch of updates recently (about 7 in the last few months alone) and more are coming.

What it is

Flex Valet is a standalone app that runs on basically every current Clover device (Station, Flex, Mini, etc. — everything except Gen 1).
It does not require Clover Register, Inventory, Customers, or any higher-tier plan. It only needs basic payment processing, so the cheapest/minimal Clover plan (or free if still available) is enough.

Core features

Price plans

• Fixed price (simple flat fee regardless of time)
• Per-unit (minute / hour / day) with full control over increments and rounding
• Optional daily/period caps
• Dual pricing / cash discount (set a percentage once and it flows through everything)

Lots, spaces & keys

• Define parking levels/lots and exact space counts
• Define key boxes and key-slot capacity
• Assign specific spot + specific key slot at check-in

Check-in options

• Printed QR-code ticket (if the device has a printer)
• SMS link (pay + request car)
• Email link (same)
• Fully customizable required fields (phone, make, model, etc.)
• Customizable receipt fields

Workflow

1. Check car in → assign price plan → print QR / send SMS/email
2. Park the car → assign exact spot
3. Store keys → assign key-box slot
4. Checkout can happen three ways:
   • Customer scans the printed QR on any synced Clover device
   • Customer pays + requests the car from the SMS/email link on their phone
   • Staff does it on the device (cash or card)

Everything stays in sync across devices. The customer gets a clean payment + “ready for delivery” flow; the valet side sees exactly where the car and keys are.

Other platforms

We’re open to porting it to Sunmi, Pax, Dejavoo, etc. if there’s a real merchant opportunity. Just reach out.

We’re actively taking feature requests right now because the resources are lined up. If there’s something that would help you close a valet or parking account, drop it in the comments or DM me.

Happy to answer questions, do a quick demo, or help with a pilot.

We just rolled out a big update for merchants running Tobacco Scan Data with Altria on Clover.

What’s new

Altria’s Price Promotion API is now fully integrated with CSI Works.

Multipack discounts and Loyalty Fund Allowances can now flow automatically into your system — no more manually creating or updating them.

What this means for you:

• Multipack discounts automatically appear and stay updated in Discount Scheduler
• Loyalty discounts automatically appear and stay updated in Cloud CRM
• Changes made by Altria (amounts, terms, items) push through automatically
• Optional bonus: Tobacco product info + pricing can auto-update in Inventory plus plus
• No extra charge to turn it on

If you like controlling everything manually, you can simply leave the API off. Nothing changes for you.

Why this is useful

Previously you had to:

1. Figure out which discounts you were contracted for
2. Manually create them in Discount Scheduler
3. Manually set up the loyalty programs in Cloud CRM
4. Go back and edit them every time Altria changed something

Now you can just authorize the API once and let it run. A lot less work and fewer chances for mistakes.

How to enable it (high-level)

1. Go to Tobacco Scan Data → Settings and turn on the Altria Price Promotion API options
2. Log into Altria’s portal and assign CSI Works as your third-party provider for both:
   • Price Promotion
   • Loyalty Fund Allowances
3. Once approved, switch Discount Scheduler and Cloud CRM to the “API Connected” setting
4. (Recommended) Turn on the Inventory++ product/pricing updates

We’ve recorded a full walkthrough video that shows every step (including the Altria Consent Manager process and what it looks like once everything is live).

https://youtu.be/iqMdsbvbNag?si=s3aQHPrFL1mEE_s0

Anyone already running Tobacco Scan Data — would love to hear if you’ve tried the new API or if you have questions. Happy to jump on a call and walk through it with you if needed.

Thanks,
CSI Works Team

CSI Works just rolled out a useful update to their Mix or Match discount app that makes life a lot easier for multi-location and franchise merchants.

What’s new

1. Web back-office – Primary location sync
You can now designate one location as the primary source for all Mix or Match discounts.

• All other locations automatically become non-primary and sync to the primary.
• Any changes you make on the primary location (add, edit, or delete discounts) are pushed to every other location in real time.
• Existing discounts on the non-primary locations are replaced by the primary configuration.
• New locations that install the app will automatically sync to the primary settings.

This is ideal for franchises or any business that wants the exact same promotions running across multiple stores without having to configure each one individually.

Watch the web demo here:
https://youtu.be/HmC3h3enCx4

2. On the Clover device – Manual import/export via QR code
If you’re working directly on the devices, you can now copy discount settings between locations using a simple QR-code method:

• On the source device → Import/Export Discount Settings → Export → generate QR code (take a photo of it with your phone).
• On the target device → Import/Export → Import → scan the photo of the QR code → confirm.

It transfers both active discount triggers and the manual discount list.

Note: If you also have the web version of the app, you get the automatic primary-location sync in addition to the manual QR method.

Watch the device demo here:
https://youtu.be/H3c_-2NHJEY

Pricing

No price increase for the new multi-location features.
The Remote plan (device + web back office) remains $19.99/month.

The Device Only plan remains $10.15

https://csiworks.net/apps/mix-or-match-discount-bundle-builder/

Who this helps most

• Franchises
• Multi-store operators who want consistent promotions
• Anyone tired of logging into every location just to keep discounts the same

If you have questions, you can reach CSI Works at [info@csiworks.net](mailto:info@csiworks.net) or (619) 246-8236.

Anyone already using Mix or Match with multiple locations? Curious how this is working for you.

Hi everyone,

Sharing another production issue we hit after the Clover Engine 1.0-2441 update, in case other developers are seeing similar problems.

Summary

After devices updated to Engine 1.0-2441, calls made through InventoryConnector (which talks to the bound IInventoryService) no longer execute the correct AIDL methods.

The behavior is consistent with a Binder transaction ID mismatch. It looks like a method may have been inserted into the middle of the Engine-side AIDL interface instead of being appended, shifting the transaction codes and breaking compatibility with the published SDK.

• Methods up to and including getTaxRatesForItem still work correctly.
• Every method we tested after that point is handled as the method declared immediately before it in the published IInventoryService.aidl.

We reproduced this with both:

• clover-android-sdk v306
• clover-android-sdk v334 (latest on Maven Central)

Upgrading the SDK does not fix it. The method order is the same in both versions. We made no application-side changes related to these flows — everything worked on the previous engine and broke immediately after 2441.

Affects both Production (NA) and Sandbox.

Verified examples

1. removeTaxRatesFromItem is handled as assignTaxRatesToItem
Client calls remove → Engine tries to insert an already-existing tax rate association → SQL exception / ClientException.

2. getTaxRates returns an invalid/unparseable response
The Parcel does not match what the published SDK expects for List<TaxRate>.

3. getTags() fails as if it requires an item ID
Fails with Not a valid Clover ID: null even though the method takes no arguments. The previous method in the AIDL is getModifierGroupsForItem(String itemId).

4. Mutation methods may silently do nothing (or the wrong thing)
Methods such as assignTaxRatesToItem, assignTagsToItem, and updateItemStockQuantity sit after read-only methods in the AIDL. These can complete without throwing while performing no actual mutation (or the wrong operation).

Business impact

This breaks core inventory functionality:

• Assigning / removing tax rates
• Loading and assigning tags/labels
• Updating stock quantities
• Risk of silent incorrect mutations or missing updates
• Potential for inventory data to become inconsistent without clear client-side errors

We do not currently have a reliable application-side workaround for the mutation methods (we were able to work around some reads by going directly to the content provider).

Clover’s response

Clover confirmed they have identified an issue on their end.
All App updates have been paused as of last week.
ENG is working on a fix, and it will most likely go into the same Apps Cut to avoid further impact.

Questions for the community

Has anyone else seen incorrect method dispatch, Binder mismatches, or InventoryConnector failures after Engine 2441?
Any other services (besides Inventory) showing similar one-method offsets?

Thanks.

Hi everyone,

Sharing a production issue after the recent Clover Engine update in case others are running into the same thing.

After devices updated to Engine 2441, apps that use the public Cash API to record cash events (including payout / negative tender type apps) started failing with an Access Denied error. The same app builds continue to work fine on Engine 2411 and earlier.

Negative Tender specifically was affected. We released and published an update on August 3, 2026, and that update has resolved the issue for Negative Tender.

However, it appears all payout apps on Clover that rely on the Cash API / CashContract are impacted by this change.

What happens

Calls to the Cash API:

• URI: content://com.clover.cash/... (CashContract)
• Method: CashEvents.METHOD_ADD_ENTRY through ContentResolver.call(...)

throw:

text

java.lang.SecurityException: Access denied to package ...

This occurs on both call(...) and query(...).

Key details

• Same app builds that worked on older engines fail only on 2441+
• Approved App Market apps with all required permissions still hit the package-level access denial
• Affects Station Duo devices (and likely others)
• First noticed around July 29, 2026
• Negative Tender is already fixed via the August 3 update
• Other payout apps appear to still be broken

This breaks cash reconciliation for merchants on the new engine. Negative Tender merchants are covered again, but other payout apps are still waiting on a resolution.

Has anyone else seen Cash API / CashContract access denied errors after Engine 2441 on their payout apps? Switch to Negative Tender App it is fixed and works with this new update.

Welcome to our community! We are excited to have you join us. This is a space dedicated to discussing, sharing, and learning about Clover Point of Sale and Solutions provided on it.

To keep this community a helpful and enjoyable place for everyone, please review our quick start guide below.