QR code control room: repoint printed codes without reprinting

I want a control room for every QR code we have out in the physical world. Once a code is printed on a poster, a van or a packaging run we cannot reprint it, but we can still change where it points. Build me an app that my field marketing, retail and events teams open whenever a destination goes dead or a season ends.

The main view is an inventory table of our codes. Each row shows the code title, whether it is a standalone QR code or a bitlink-backed one, its current destination, total scans over the last 30 days, and a small trend line of daily scans across that window. Let me filter the table by campaign tag, and let me sort by scans so the strongest and weakest placements are both easy to find. Keep the table dense and scannable rather than card-based, because we may have hundreds of codes.

Important constraint on how you assemble that table. Bitly has no single operation that lists all QR codes, so do not build as if one exists. The inventory has to be stitched together from two reads against our group: Retrieve Bitlinks by Group gives the bitlink-backed QR codes and can be filtered by tag, and Retrieve Top Links and Decoupled QR Codes by Engagements gives the standalone or decoupled codes in the same group. Merge those two sets into one list and mark each row with its code type, because the type decides how repointing works later. Get the group identifier from the connected account, and use Retrieve Tags by Group to populate the campaign tag filter rather than making me type tags from memory.

Per-code numbers come from two more reads. Use Get QR Code Scans Summary for the 30-day scan total on each row, and Get QR Code Scan Metrics for the daily time series behind the trend line. When I open a single code, use Retrieve a QR Code for its metadata and current destination, and Retrieve a QR Code Image so I can see the actual printed artwork next to the placement details and confirm I am looking at the right code.

Join every code to a placement register kept in Google Sheets and read with Get Values. That register is the piece Bitly itself does not store, and it carries real weight here: it holds where the code is physically installed, the print run size, the install date and the owner. Match register rows to codes on the short link or code reference column. A row should read something like lobby poster, Manchester office, 500 printed, installed March, owned by Priya, and those fields belong right next to the scan numbers in the table. Any code that exists in Bitly but has no register row should be flagged as unregistered so we can fill in where it actually went.

The key action is repointing. I select a code whose destination is dead or seasonal and update it in place. Repointing differs by code type, so branch on the type you recorded earlier. Standalone codes use Update a QR Code Redirect, which changes where the code redirects without changing the image. Bitlink-backed codes are repointed by changing the underlying link with Update a Bitlink, which updates the destination along with title and tags. Put both behind one confirmation step that shows the current destination next to the new one, side by side, along with the placement and print run size so I can see the blast radius before I commit. After a successful update, refresh that row in place so the new destination is visible immediately. Also offer Convert a QR Code to a Bitlink for the case where a standalone code needs to become trackable as a link.

Flag two problem states prominently, as counts at the top of the page that act as filters on the table. First, codes with zero scans in the last 30 days, which usually means the placement is wrong or the code never shipped. Second, codes still pointing at an expired campaign page. For the expired case, let me maintain a short list of expired or seasonal destination patterns, and match each code's current destination against it so the app can tell me which printed assets are still sending people somewhere we retired.

Let me also create a code for a new placement. The form takes the destination, a title, a campaign tag and the placement fields, then calls Create a QR Code. Use that full-featured operation rather than the static one, because it returns a trackable code and tracking is the entire reason we can repoint and measure these. Once the code is created, append its row straight back to the register with Append Values, carrying the code reference, short link, destination, placement description, site, print run size, install date and owner, so the register never drifts from what is actually in Bitly.

One plan nuance to handle gracefully. Custom branded bitlinks and some QR features require a paid Bitly plan and return a permission error otherwise. When that happens, show a calm empty state explaining the feature needs a paid plan instead of surfacing a raw error or breaking the rest of the table. The inventory, scans and repointing should keep working regardless.

Everyone on the team sees the same inventory, so no per-user filtering is needed, but the app should feel like a working surface rather than a report: the point is that someone spots a dead code and fixes it in the same screen, in under a minute.