Dekornata
A handmade furniture workshop selling nationwide, without a person chasing every order.
What we delivered
- Web
- Mobile app
- Admin dashboard
- Backend & APIs
Capabilities applied
- 01
A customer orders, at any hour
- 02
Freight priced per destination and per item
External systemLive courier network rates - 03
Payment settles and drives the order state
- 04
The order enters the production queue
Nobody quotes, confirms or chases anything. The order that used to cost a person a day of messages now costs the system a second.
Solid outline: built and run by us. Dashed: an external system the flow depends on.
The business
Dekornata builds furniture by hand in Indonesia — made-to-order pieces, each one a little different from the last. They sold well locally, through a showroom and conversations over chat. Selling across the country turned out to be a different problem entirely: the further a wardrobe travels the more the freight costs, and every order had to be quoted, confirmed and chased by a person.
The challenge
Furniture is close to the worst possible category for e-commerce. It is heavy, bulky, expensive, made to order, and sold on photographs rather than specifications. Four problems had to be solved before a single online sale could work.
- 01
Freight cost is the whole business case
A wardrobe going to the next district and the same wardrobe crossing to another island are not remotely the same cost. One flat shipping rate either loses money on every distant order or frightens off the nearby customers who should have been the easiest sales. Quoting by hand does not scale, and getting it wrong on a heavy item erases the margin on the piece.
- 02
Every piece is a variant
Handmade means finishes, dimensions and materials shift between production runs. The catalogue had to be reshaped by the workshop team as they worked — not by a developer running a deployment every time a finish changed.
- 03
Buying furniture is a trust decision
Nobody spends a month of salary on a wardrobe from a page that loads slowly or shows four pixelated photos. The storefront had to carry heavy photography convincingly, over the mobile connections most Indonesian customers actually browse on.
- 04
Orders were living in chat threads
Payment, confirmation and delivery status were tracked in message history and memory. With no system of record, nothing could be reported on and anything could be forgotten.
What we did
We built the storefront and the operational system behind it, across web and mobile, so an order placed at midnight is priced, paid for and queued for production without anyone touching it.
What we built
Real-time freight pricing across Indonesia
Shipping is calculated at checkout per destination and per item against live courier network rates, so the price a customer sees is what the piece actually costs to move. This was the hardest part of the build, and the part that made selling nationally viable at all.
Payment tied to order state
Payment gateway integration where the payment result drives the order lifecycle: settled orders enter the production queue on their own, and abandoned ones expire on their own, instead of living in someone's head.
A catalogue the workshop runs itself
Product and variant management built for made-to-order goods — finishes, sizes and materials configured by the team, with no developer in the path.
A storefront built to be found
Server-rendered product pages so every piece is indexable and shareable, with an image pipeline that keeps heavy furniture photography fast on a phone.
A mobile app on the same spine
A cross-platform app sharing one catalogue, one pricing engine and one order system with the website, so the two can never disagree.
Inventory, tracking and reviews
Stock levels, fulfilment status, customer-facing order tracking and reviews, behind an admin view the team uses daily rather than avoids.
Tell us what you are trying to solve
Chat on WhatsApp