Internal tool · Prototype · No login

Pricing Admin — Memory Strip Roll

Set and schedule pricing for the Memory Strip Roll (50 labels per roll). Nothing here is published automatically — prices stay hidden from customers on the Shop page until you fill them in and click Approve & Publish below.

This is a prototype with no real security

There is no username, password, or access control on this page — anyone with this URL can view and change these settings in their own browser. Settings are saved only in this browser, on this device, using local storage — they are not stored in a shared database, so changes here won't appear for other people or other devices. See "How this works" at the bottom of this page for what a production version would need.

Product

Memory Strip Roll

50 tamper-evident labels per roll · memory-strip-roll

Manufacturing cost

$7.50

per roll · internal reference only

$

Leave blank to keep the Shop page showing "Pricing coming soon."

No quantity discount tiers yet. Every roll uses the regular retail price until a tier is added.

A tier applies once the cart reaches its minimum quantity — for example, "10+ rolls → price per roll."

$

To schedule a promotion, fill in all three: promotional price, start date, and end date. While active (both dates inclusive), the promotional price overrides the regular price and any quantity tiers.

Publish status

Draft — not visible to customers

Click Save Draft to store your work privately — the Shop Memory Strips page keeps showing "Pricing coming soon" no matter what values are entered above. Click Approve & Publish only when you want that pricing to appear on the Shop page. Approving never enables checkout — online ordering stays disabled either way.

Not saved yet. · Checking browser storage…

Live preview

Updates as you type

Memory Strip Roll

50 labels per roll

Pricing coming soon

Pricing coming soon

Retail price has not been approved.

Shop page status

Not visible to customers yet — set a price, then click "Approve & Publish."

How this works — read before relying on it

Storage and security limitations

  • No real login. This page has no username/password or access control of any kind. Anyone who opens this URL can view and change these settings for themselves.
  • Stored only in this browser — when storage is available. Pricing is saved with your browser's local storage, on this device only. It is not a shared database — a change made here only appears on the Shop page when viewed in this same browser, and is never synced to other visitors or devices.
  • Why this preview may say "browser storage unavailable." Many embedded code-preview tools load this page inside a sandboxed frame, and sandboxed frames are blocked by the browser itself from using local storage — that's a restriction of the preview wrapper around the page, not a bug in this page's code. When that happens, Save Draft, Approve & Publish, and Clear all pricing still work for the rest of your visit (held in this browser tab's memory), but every value resets the moment you leave or reload the page. This page always tells you, after every action, exactly which of those two cases just happened — it never says something is "saved" when it is really only sitting in memory.
  • How to test real persistence. Open this file directly in a normal, top-level browser tab — not embedded inside another page or preview frame. In most editors/hosts that means using an "open in new tab" action or visiting the page's own URL directly, rather than viewing it through an embedded preview pane. Once opened that way, local storage is almost always available, and you can confirm persistence yourself: click Save Draft, then close the tab (or reload the page) and reopen admin.html — your values should still be there, and the status line under the buttons will read "available," not "unavailable."
  • Not encrypted, not audited. There is no record of who changed a price or when, beyond the "last saved" time shown above, and nothing here is encrypted at rest.
  • What a production version needs. A server-side database to store prices centrally, authenticated admin accounts with role-based permissions, HTTPS everywhere, and an audit log of pricing changes — none of which exist in this prototype.