Zeynep Aslı Erhan

Work

Shopify storefronts and the systems behind them first, then products and platforms, each told as problem, constraint, approach and result. Kremi, my own products and the white-label sites are named; other client systems stay anonymous.

Kremi

Kremi is a cosmetics e-commerce brand. I work with them as their software consultant on the app, the website and the systems behind the orders.

  1. Kremi · Mobile e-commerce + video feed

    Making a video feed scroll smoothly on a phone

    Three data sources (a storefront, a backend and a video feed) combined into one app that stays smooth while scrolling.

    Still from the animation built from a screen recording of the Kremi app on an iPhone, in Turkish: the video home screen, best sellers, the Community video feed with the creators' faces blurred, the Makeup collection, the Kiss'n Blush product page with a shade change, and a search for blush

  2. Kremi · Shopify theme engineering

    A storefront built to the brand, not to the theme

    Custom Liquid sections and interactive components for Kremi's Shopify store, in Turkish and English.

    Still from the animation built from the Kremi website's English storefront on Shopify: best sellers, the header heart opening Favorites, the Products menu, the Masks page, a product card on hover, a product page with a variant switch and the cart drawer

  3. Kremi · Order & shipping automation

    Designing an order pipeline that cannot fail silently

    An order pipeline for the online store and three marketplaces that turns failure into an alert instead of a silent gap.

    Still from the abstract animation of Kremi's operations systems, with no real screens or data: orders from the online store and three marketplaces flowing into one queue, then email notifications, shipping, reviews, returns and the operations panel that ties them together

  4. Kremi · Ongoing systems partnership

    The operations panel a growing store runs on

    Long-running development partnership with Kremi: an operations dashboard for orders, stock, barcodes and shipping, growing feature by feature.

    0API keys in the browser

Products

  1. FolderPls · Tag layer for Google Drive

    Organizing Google Drive without moving a single file

    Tags laid over Google Drive, filtered and mapped in a graph: tagging moves no file, and Drive's own permissions still decide who sees what.

    Still from the animation built from screens of the FolderPls panel with invented sample files: AI tagging started with a button, labels appearing on Drive files, then the files mapped in a graph

  2. LinkZae · Digital business card platform

    One codebase, a separate site for every tenant

    Digital business cards and link pages, each customer served from their own subdomain resolved before the page renders, with one QR code per card.

    Still from the animation built from LinkZae's own interface, as shown on its site: a digital business card designed, its QR code printed and the contact saved

  3. PromptLikeEngineer · Version-controlled prompt library

    Giving prompts real version control, on Postgres

    Version control for prompts: every save is a version you can diff and roll back from the terminal, the web or an agent, and each team's prompts are isolated by the database.

    Still from the animation built from PromptLikeEngineer's own interface, as shown on its site: two versions of a prompt compared and one rolled back

  4. Loyalty / points engine

    Making the points ledger impossible to update wrong

    Balance is a sum of history, not a column, so double-awarding points is architecturally impossible.

    97row-level security policies

  5. White-label site platform

    Turning agency repetition into one product

    One shared database, a clonable frontend, tenant isolation enforced by a JWT claim.

    30row-level security policies

  6. AI-OS · Agent layer

    Keeping “done” and “live” from meaning the same thing

    14 department agents, read-only knowledge access, a two-repository architecture.

    14department agents

Client systems

  1. Inherited system modernization

    Finding the silent data loss in a platform I inherited

    The panel said “commission updated”; row-level security had silently rejected the write. It was the most valuable find of a five-month live migration.

    Brand kept confidential
    5months with the system live while the database was replaced

White-label sites

Sites running on one white-label site platform I built: a shared database and a clonable template.

How the platform works