The first version of Woxly was three surfaces on one commerce core.

Indian sellers were already selling. Inventory lived in a sheet. Orders lived in WhatsApp and Instagram DMs. Payment was a Razorpay link or cash on delivery, reconciled at night. The store was a reputation.

Existing tools assumed a team. Shopify-shaped products assumed a catalogue, a theme, and someone to run apps. The people I was watching had a phone, a supplier, and a chat thread that was also their CRM.

woxly.store gets a seller from a name to a live checkout without a developer. The landing page converts into onboarding.

app.woxly.store is ops. Orders, stock, status, staff roles, exports. If this screen is confusing, the storefront does not matter.

{name}.woxly.store is what the customer sees. Brand, cart, Razorpay, COD, then a handoff into fulfillment. Tenant-aware routing keeps merchant data isolated without cloning the whole app.

Payments had to be boring. Razorpay and COD sit in the same order lifecycle, so the seller does not forget to reconcile a plugin.

I also wrote the docs so an agent can read them. Paste https://docs.woxly.store into Cursor or Claude and scaffold a storefront from the API. The seller should not need me in the loop to stand the shop up.

I would not ship a heavier theme marketplace, or anything that looks like an enterprise suite. The constraint is still a person running a business from a phone.

If you are moving off DMs and want a store that is actually ops, start at woxly.store. If you need a Next.js product or marketing site built the same way, email contact@sanjid.in.