Skip to main content
← Blog
3 min read

Clover's 2026 Holiday Code Freeze: What's Locked and What to Finish First

By Yan Payments

When is Clover’s code freeze and what does it cover?

Clover’s 2026 holiday code freeze runs from November 10, 2026 through January 3, 2027. During that window, Clover doesn’t update its APIs, SDKs, or other platform services, and it doesn’t approve any new apps for the App Market, full stop. The freeze also covers third-party apps built on Clover’s APIs and SDKs, so any integration work that depends on a platform-side change is effectively paused too.

The point of the freeze is stability. Clover locks the platform down during its busiest sales weeks of the year so a rushed update or a buggy app approval doesn’t take down checkout on Black Friday.

Is there any exception during the freeze?

Yes, a narrow one. From December 7 to December 9, 2026, Clover will accept new APK submissions, but only for critical issues or security vulnerabilities that directly affect your integration. Even then, those submissions get extra review and require justification before they’re approved. This isn’t a window to sneak in a feature update or a UI tweak. It’s strictly for “something is broken or unsafe and it needs to go out now.”

Outside that three-day window, and for the rest of the freeze, nothing new gets approved, regardless of urgency framed as “but it’s a small change.”

What should you finish before November 10?

If you’re a Clover merchant planning any of the following, get it done before the freeze starts, not during the holidays when you’ll need everything working:

  • New hardware setup or terminal swaps, including provisioning new devices
  • Installing or updating any third-party app from the App Market
  • Integration changes tied to a POS add-on, like a new loyalty program, online ordering tool, or accounting sync
  • Menu, catalog, or pricing structure changes that depend on an app update rather than just editing items in your existing setup

A good rule: if the change only touches your own data, like prices, items, hours, or staff, you can usually still do that during the freeze, since that’s normal day-to-day use, not a platform or app update. If the change depends on Clover or a third-party developer pushing new code to your device, that’s what gets stuck.

What still works normally during the freeze?

Day-to-day operations aren’t affected. You can still process payments, run reports, manage inventory counts, add or edit items, and use every app you already have installed. The freeze blocks new approvals and platform updates, not your existing setup. Clover’s own support lines also stay open during the freeze, just with the understanding that anything requiring a platform-side fix will wait unless it qualifies for the critical or security exception.

What if something breaks during the freeze?

Contact Clover’s Developer Relations team at developer-relations@devrel.clover.com if you’re a developer, or your normal support channel if you’re a merchant. Routine bugs and feature requests queue up until after January 3. Anything that qualifies as a security vulnerability or a critical, integration-breaking issue can still move, just through the tighter review process described above.

Bottom line

Treat November 10 as your real deadline for any Clover-side changes this year, not January 3. If you’re thinking about new hardware, a new app, or an integration change for the holidays, get it done now. We help merchants plan hardware changes around freezes like this one so nothing’s mid-install when the busiest weeks of the year hit. Reach out if you want help getting ahead of it.

Sources: Clover Developer Docs, “Announcing 2026 Clover code freeze” (docs.clover.com)


← Back to all posts