Commerce . Custom stack

Rekordroom

A vinyl shop with a full custom stack, from intake to checkout to Instagram

records in stock: 387records in stock
to checkout: Intaketo checkout
hosted stack: Selfhosted stack

rekordroom.com

The Rekordroom vinyl storefront home page with its curated collection

Status. Live at rekordroom.com. Site and checkout fully operational.

What it is

A curated secondhand vinyl shop in Kozhikode, Kerala. The public site is a statically generated catalogue spanning Bollywood to ghazal to rock, with cart and checkout built entirely in the browser.

The problem

A founder-run shop has no IT team and no budget for a large commerce platform. It still needs a fast, search-friendly storefront, a simple admin for stock, and a social presence that posts daily without manual effort.

What we built

A custom static site generator that reads a database and builds every product and category page, optimised images included, ready to deploy.

A lightweight admin for inline editing, image upload, order management, and a one-click rebuild.

A client-side cart and checkout with no payment processor and no server session, confirmation emails sent straight from the browser.

An inventory pipeline: photograph a record, run one script, and AI vision extracts the artist, label, and condition straight from the cover image.

Automated Instagram reels: a short video rendered from record photos, matched background music, posted on a randomised multiple-times-daily schedule.

A pricing engine that cross-references multiple marketplaces with genre, rarity, and condition multipliers.

Notable engineering

AI-assisted intake that turns a raw record photo into structured catalogue data in seconds instead of minutes.

A fully stateless checkout: the entire purchase flow runs client-side, with two transactional emails fired from a single form submit and no backend at all.

Randomised scheduling generated programmatically to avoid platform pattern detection, rerunnable any time the posting windows change.

A silent scheduling failure root-caused by querying the CI provider's job API directly after the standard log view came back empty, tracing it to a token expiry and changing the token architecture as a result.

Stack

PythonSQLiteFlaskNetlifyRenderGitHub ActionsClaude

Capabilities demonstrated

Custom static site generation as a commerce platformAI vision for product intakeServerless checkout with no payment processorMulti-post-per-day social automationMarket-aware pricing enginesFounder-operable inventory pipelines

Have a build in mind?

Tell us what you are trying to ship. We will tell you plainly whether we are the right fit.

Start a conversation