When the POS Terminal Becomes the Boss: Designing a 10-Second Black Friday Comedy
When the POS terminal becomes the boss What happens when a shop's cash register takes a Black Friday discount more seriously than the humans—or, in our case, animals—running the store? We built CASHY's Black Friday Me
When the POS terminal becomes the boss
What happens when a shop's cash register takes a Black Friday discount more seriously than the humans—or, in our case, animals—running the store?
We built CASHY's Black Friday Meltdown, a ten-second, clearly fictional 3D animated comedy set inside Meow Mart. CASHY, a sentient checkout terminal, discovers toy money and scans the orange cat owner as a product marked 99% OFF. The cat's clever spaniel partner buys his freedom with a tiny real coin. Then the register sees the fake bill again, and the cycle restarts.
The premise is absurd, but its structure borrows a useful principle from interface design: a viewer should be able to infer the system state from visible consequences.
A three-state story, not ten unrelated gags
- Exception: CASHY identifies the toy banknote and reacts by scanning its own owner.
- Intervention: The dog contributes a real coin, visibly changing CASHY's emotional state and releasing the cat.
- Regression: The original fake banknote is still present, so the alarm returns and the loop restarts.
The key is causality. Each state change has a physical trigger: scanner to barcode, receipt to price tag, coin to release, and fake money to renewed suspicion. These are easy to follow even without dialogue.
Character design carries the user interface
CASHY is more than a prop. Its screen is a face: red angry eyes communicate rejection; golden dollar-sign eyes communicate payment accepted. Its mechanical arms operate the scanner, and the receipt slot behaves like a mouth. The cat's panic and the dog's quick rescue turn the machine's state changes into character comedy.
That is a design lesson for real software as well: error handling is easier to understand when the consequence and recovery path are visible. Of course, CASHY is a fictional character, not an actual fraud-detection product or a recommended POS design.
Production details and constraints
The episode uses an owner-approved first-frame character reference, a single recurring shop environment and a short cause-and-effect arc. The supplied source was 720×1280 at 24fps. The final delivery was formatted at 1080×1920, 24fps and exactly 10.000 seconds; scaling an image does not invent true native 1080p detail.
One permanent, mobile-readable question—WILL CASHY SELL THE CAT?—is added in postproduction rather than relying on the video generator to render typography. The edit uses original cartoon effects, not spoken exposition.
Our media-production SOP preserves the source and records the edited video through real-time FFplay playback, Xvfb display capture, FFmpeg and ALSA audio capture. We retain technical evidence and provenance: a playback recording does not make an AI-assisted cartoon non-AI or eliminate applicable disclosure requirements.
What we would measure
For a ten-second comedy, view counts alone do not validate the creative hypothesis. A useful post-release review would check whether viewers understand the first-second conflict, whether retention survives the coin-rescue reveal, whether the 10-to-0 loop works in the actual exported file, and whether people follow the characters into another episode.
This is a small storytelling experiment, not a claim of viral success. The broader idea: memorable short-form product storytelling can start with a familiar operational failure, give it a distinct personality, and show a coherent recovery—even when the recovery is hilarious.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.