LoginSign Up
← Back to all sparks
S

Shift4

FINANCE
Velocity5.0

Reporting is where Shift4 is actually shipping; the POS feed is mostly release calendar.

reportingposrelease-calendarmulti-locationdevice-migrationcanopy
◆Current state
Shift4's feed is a release calendar rather than a changelog: each cycle appears as pre-release notes, a canary, a patch and finally a global release, so the same version strings recur across entries days apart. In this window the Canopy 2.0 reporting work (DataNow) moved from pre-announcement on 6 August to an actual release candidate on 11 August, still carrying no new version number, while the weekly Customer Hub 2026w33 build named multi-location management and an employee shift report. A Canopy login screen change adds a Shift4 OKTA sign-in button that is meant for Shift4 staff, not merchants. Bodies are truncated to roughly 150 characters, so titles and version strings carry most of the signal.
◆Where it's heading
Two lines run in parallel. The venue POS estate is managed conservatively through staged canary-to-global rollouts plus a forced EloView 4 device migration with a 14 August customer deadline, while the reporting and back-office surface — Canopy 2.0, DataNow, Customer Hub — absorbs nearly all the visible feature work. Multi-location management in Customer Hub points at operators running several venues, the same constituency the Canopy reporting rebuild serves. The point-of-sale software itself is receiving patches and version bumps, not new capability.
◆Prediction
The Canopy 2.0 reporting release candidate should convert to a versioned general-availability build in the coming weeks, and the 14 August EloView 4 deadline is likely to generate a final reminder notice before it passes.

◆Recent moves

  1. 7d ago

    Shift4 Venue Announcement: New Button on Canopy Login Screen

    A "Sign In with Shift4 OKTA" button appears on the Canopy login screen for all users, but it is intended for Shift4 staff rather than merchants. A visible change with no action or capability attached for the operators reading this feed.

  2. 7d ago

    Customer Hub adds multi-location management and shift reports

    The weekly Customer Hub build names multi-location management and an employee shift report, both aimed at operators running more than one venue. That is the same constituency the Canopy 2.0 reporting rebuild targets, so the back-office surface is where this quarter's feature work keeps landing.

  3. 7d ago

    Canopy 2.0 reporting enhancements land as a release candidate

    The Canopy 2.0 reporting enhancements previewed five days earlier reached release-candidate status on the projected date, still carrying no new version number. It confirms reporting as the active development line while the POS side receives only staged patches.

  4. 12d ago

    Canopy 2.0 reporting enhancements pre-announced for 11 August

    The pre-announcement of the reporting release candidate that landed on 11 August, posted with no version number and nothing shipped at the time. Every other pre-release notice in this feed reads the same way: the calendar entry, not the release.

  5. 13d ago

    Shift4 Venue Announcement: EloView 4 Migration *ACTION REQUIRED BY AUGUST 14*

    Managed Elo devices behind Shift4 Venue and Appetize move to EloView 4, with a customer action deadline of 14 August. Forced infrastructure maintenance rather than product work, but it lands real operational cost on venue operators.

  6. 13d ago

    Important Update: DataNow Scheduled Report Deliveries

    A v1.3.7 bug fix for DataNow scheduled report delivery, posted a second time after an identical 3 August notice that the feed still carries. Maintenance on the reporting line the Canopy 2.0 work is meant to supersede.