Shopify · Authentication
Her-age NFTIZE — luxury authentication and a digital passport, mapped SKU to TokenID, on the current Shopify API.
NFTIZE is Her-age's internal Shopify app: authenticate a luxury item, then issue a digital passport — an NFT certificate after expertise. SKU / VariantID maps to TokenID. Manual and batch. We migrated it to the current Shopify API (GraphQL, session tokens), redesigned DynamoDB PK / SK / GSI, gave experts Next.js status tracks, put an audit trail and queues with a DLQ under the jobs, and cleaned AWS. Work restored. Server ops cost −30%.
- app work
- Restored
- server ops cost
- −30%
- new API
- GraphQL
A passport, not a mint dashboard
After expertise, the item gets a digital passport: an NFT certificate. The operational problem is the map — SKU / VariantID ↔ TokenID — in one-off and in batch. We do not publish mint counts or chain metrics. The job was to make the map and the statuses true again.
API, store, then the expert's track
Migrated to the current Shopify API: GraphQL, session tokens. DynamoDB keys redesigned — PK, SK, GSI — so lookups stop lying. Next.js status tracks for experts. Audit trail on the work. Queues and a dead-letter queue so a failed batch does not vanish. AWS: S3 lifecycle, services consolidated, the bill smaller.
- Shopify GraphQL and session tokens
- SKU / VariantID ↔ TokenID, manual and batch
- DynamoDB PK / SK / GSI redesign
- Expert status tracks on Next.js
- Audit trail, queues, DLQ; S3 lifecycle and service consolidation
Sibling of Sell with Us, not the store
This is the authentication app. The consignment app is her-age-sell-with-us. The store redesign is her-age. Three products, three cases. NFTIZE: restored work, new API, −30% on server ops.
Technologies
- Shopify
- AWS
- Next.js
- Node.js
Outcomes
- NFTIZE working again on the current Shopify API
- −30% server ops cost after AWS cleanup (S3 lifecycle, consolidated services)
- Experts get Next.js status tracks; jobs have an audit trail, queues and a DLQ
Recommended articles
Blog
The case for boring web stacks
TypeScript, Postgres and edge deployment are not exciting — they are how you still iterate fast in year three without rewriting the platform.
Blog
Shipping evals before prompts
Why we run regression suites on LLM outputs before every release — and how it changed our AI delivery cadence at ZNN.
Blog
Mobile release trains that do not break
Fastlane, staged rollouts and feature flags — a practical playbook from eighteen App Store submissions without a Friday-night rollback.
Recommended case studies
Luxury · Volume eDTL
The Brand Collector
The Brand Collector resells pre-owned luxury through a supplier network. Same class of problem as a catalogue feed — except each dump crossed 120,000 rows, and the CSV they hold sits above 169,000. Fastify stayed the orchestrator. The heavy compute moved to Go workers. About 60% faster on taxonomy, mapping and pattern-match at that volume.
iGaming · Platform
Casino operator · NDA
Under NDA we stabilised three production gambling brands: cleaned up legacy PHP/JS stacks, extracted shared modules, and shipped a new marketing site without stopping live traffic.
Marketing · Fintech
Digital DAO
Digital DAO is a marketing studio in Belarus that works mostly with fintech. We did not repaint the old site. We rebuilt the story and the visual system so it would sit in a room with banks, not with a carnival agency deck.