Complete E-Commerce Package

Description

All of it as one job: the store, the payments, and the shipping. The gateway and the carrier rates go in during the first week, so payment and delivery are tested alongside the cart while it is still being built. One schedule, one handover, one invoice. At the end the repository and every account are yours.

Details

This one is for a shop selling outside Indonesia, or a company registered abroad. The gateway and the carrier are wired to the ones your market actually uses, and the price is set for that market. It is for launching a shop that has to take money on day one, with a look and a codebase of your own.

### What only this package gives you

• A design built specifically for your shop.
• Any feature your workflow needs, as long as we agree it up front.
• The repository becomes yours. You can carry on with anyone afterwards, including without me.
• The gateway and carrier rates are in from week one, so payment and delivery are tested together with checkout while it is still being built.

### The store

• Next.js App Router, rendered on the server, so each product sits on its own URL that Google can read.
• Catalog with categories, search, and stock tracking.
• Cart and checkout.
• An admin you can run yourself: products, categories, stock, orders.
• Customer accounts: sign-up, sign-in, order history, and saved addresses so the next order is quicker.
• Automatic confirmation emails to the buyer whenever the order changes state, and a Telegram alert to you the moment one comes in.
• Layout adapts to the screen, with light and dark modes.
• SEO groundwork: sitemap, structured data, and Open Graph images.
• Visitor analytics, so you can see how many people arrive, where from, and which pages they actually read.
• The shop installs onto a phone's home screen like an app, with its own icon and no browser chrome. There is no separate app to build and nothing to submit to an app store.
• Push notifications to the buyer's phone when their order changes state, over VAPID. They arrive as system notifications like any app would, and tapping one opens the order itself.
• Core Web Vitals in the green on the launch build.
• Deployed to Vercel on your own domain, with SSL.
• Repository and every account handed over to you at the end.
• Two rounds of revisions, as long as they stay inside the scope we agreed.
• Thirty days of bug fixes after handover.

### The payments

• One gateway: Stripe or PayPal. Which one is decided at the first call, based on where your company is registered and how your buyers prefer to pay.
• The methods you actually want: cards, digital wallets, bank debit, and the local methods your gateway offers in your markets.
• Amounts recalculated on the server. A price sent by the browser is ignored.
• Webhooks with signature verification, safe to receive twice. A repeated notification cannot charge or fulfil the same order again.
• Recovery for payments whose notification never arrives. Gateway notifications do go missing, and without this you hear about it from a customer who has already paid.
• Order states wired all the way through: waiting, paid, expired, failed. Stock that was held returns on its own the moment a payment dies.
• Payment records kept on the order itself, so a customer who closed the tab can pick it up later.
• Everything built against sandbox first. You test each method, and only once you say it works does it move to production.

### The shipping

• Shipping through EasyPost, or whichever carrier API serves your region best. We settle that at the first call: a US shop and an EU shop rarely want the same one.
• Live rates at checkout, calculated from weight, dimensions, and the destination address, so the buyer sees a real total before paying.
• Every service the route actually offers, priced live, so nobody has to guess at a flat fee.
• Labels are bought and the tracking number lands on the order the moment it is paid, and the status keeps updating there by itself, so nobody has to go and check the carrier's site.

### Not included

• Merchant registration and platform onboarding. The account stays in your name, and so does the money.
• Gateway transaction fees and settlement.
• Carrier accounts and postage costs.
• Sales tax and VAT registration. A gateway moves money. It does not register you anywhere. If you sell to consumers across borders, that is a merchant-of-record decision, and we talk it through before you commit.
• Product photos, copywriting, and typing your catalog in.
• A native app for the Play Store or App Store. What you get installs like an app from the browser, which is a different thing.
• Migrating data out of your existing shop, whether that is Shopify, WooCommerce, or something else. I can do it, but I price it separately once I have seen how much there is and what shape it is in.
• Hosting, domain, and third-party fees. All of it stays in your name.
• Anything we did not agree on at the start. If you ask for more mid-project, I price it before I build it.

### If you cancel partway

You get your money back. What I keep is only the part I have actually done. I will show you what that is, with the work to prove it.

The reasoning is simple: holding money for work I have not performed is not mine to hold. Work that is finished has earned its fee.

Whatever is built is still handed over: the repository as it stands, with a note on where it got to.

### Stack

The auth and database rows are not locked in here. We decide them together at the first call, weighing what your team already runs against what the catalog actually needs.

Process

1. First call. We go through what you sell, who buys it, and what has to be working on launch day. I do not bill for it, because this is where the scope actually gets set. 2. Written proposal. Scope, price, and a schedule with dates on it. I do not start until that is in your hands. 3. Agreement. You pay 50% to begin, the rest at handover. 4. Build. Storefront and catalog first, then checkout with the gateway and live carrier rates wired straight into it, and the admin last. Every week you get a report and a link you can open. 5. Review. You get two rounds of revisions inside the scope we agreed. You also confirm every payment method works in sandbox before the production keys go in. 6. Handover. Repository, deployments, and admin accounts move to you, and I stay alongside until you can run it yourself. Final 50% at this point. 7. Support. Thirty days of bug fixes at no extra charge. A bug means something does not match what we agreed. If what you are asking for turns out to be a new idea, I will say so. Past those thirty days you can still call on me. Each request is priced on its own, and I tell you the figure before I start.

Reckon on 4 to 6 weeks from the day the deposit lands, provided your answers come back within two working days.

I work per project, not per hour. Meetings are not on the clock.