Aug 2026: a breach at Trezor's shipping partner exposed the home addresses of nearly 12,000 customers. Read why →

Notes from our first 100 encrypted orders

What broke, what did not, and what we changed before opening the beta.

Oct 2, 20261 min read

The setup

We ran the first hundred orders through one store and one warehouse. Real buyers, real addresses, real carriers. The goal was to find the boring problems before anyone else did.

What worked the first time

  • Checkout. No buyer contacted the store about it.
  • Picking. Staff adapted to tokens in a day. The most common comment was that the pick list was easier to read.
  • Deletion. Every delivered order had its address deleted, with a record, within the expected window.

What broke

Issue Cause Fix
Two labels printed blank Printer driver cached an old template Label client now clears the template on start
One order stuck as Encrypted Carrier webhook never arrived Daily reconciliation with the carrier API
Support asked for an address Habit Correction link added to the help macro

What we changed

The biggest change was not technical. We rewrote the setup guide so the first test order happens before the warehouse is connected. Seeing an encrypted order in your own admin explains the product faster than any page we could write.

Next

The beta is open to a small group of stores. If you ship sensitive products and want to be one of them, get in touch.