Skip to main content

Services

Custom systems, e-commerce:
what's included, what isn't

Two lines of work, five stages, six kinds of deliverable. This page states the scope plainly — what is included, what is not, and roughly how long. Reading it before we talk saves about two meetings.

Talk about a project

Two Lines

What each line covers

A rebuilds the part of your operation that no longer reconciles. B puts up a site that can actually sell. Most projects need only one of them; the ones that need both usually have physical stores and are opening online.

A

Custom system development

Stock that never reconciles, orders overwritten, invoices still issued by hand. We redraw it from the data model up, then stay with you for three months after it goes live.

Who it fits
  • You are already operating, with real data volume, and the way you work now is starting to produce errors or slow you down
  • The same record gets written down in two or three places, and month-end reconciliation is done by hand
  • Off-the-shelf software gets you most of the way there, but cannot be changed for the last mile
  • Several stores and several roles, where each person should see only their own slice
What's included
  • The data model and table structure redrawn, not patched onto the existing system
  • Back office screens, role permissions, audit trail
  • Payment and e-invoice integration, reconciliation and report export
  • Migration of your existing data, checked record by record afterwards
  • Switchover on launch day, and three months alongside you after handover
What you receive
  • A system you can run the business on, and the back office accounts
  • The table structure and a field-by-field description
  • A launch runbook and the rollback steps
  • Operating instructions and handover documents
  • The source code
Not included
  • Hardware purchasing and on-site cabling
  • Brand identity and graphic design
  • Product photography and copywriting
  • Running your operation for you (shipping, customer service and listing products stay with you)
  • Native iOS / Android apps
B

Websites and e-commerce

It takes orders, lists products, and lets you edit your own copy. Payments, e-invoicing and accounts are wired up, so you can start selling on handover day.

Who it fits
  • You are about to start selling, and payments, e-invoicing and accounts all have to be in place at once
  • Your current site cannot take orders, or the back office cannot be changed and every wording edit needs someone else
  • You have physical stores and want the website and the counter on one stock ledger
  • You need a site that Google and AI crawlers can actually read, not one large image
What's included
  • Front-end pages, and the content you can edit yourself
  • A back office for products, orders and accounts
  • ECPay or PayUni payment integration, with end-to-end testing
  • E-invoices issued, voided and credited
  • LINE Login, notifications and scheduled jobs
  • SEO structure, domain setup and deployment
What you receive
  • A site you can list products on and start selling from
  • Back office accounts and permission settings
  • The payment and e-invoice test records
  • Operating instructions and handover documents
Not included
  • Opening the payment and e-invoice accounts themselves (they have to be in your company's name; we sit with you through the forms and the testing)
  • Product photography and product copy
  • Ad buying and SEO as a managed service
  • Cross-border payments and multi-currency checkout

How We Build

Every stage ships something

Five stages, from scoping to operations. The chart below is the real delivery weighting: stages across, what you receive down.

Deliverable
01ScopeAgree what we will not do
02ModelDraw the tables before the code
03BuildSomething you can click every two weeks
04LaunchA runbook for switchover day
05RunSomeone picks up when it breaks
Scope and requirements
Table structure
Screens and flows
Integrations and payments
Testing and acceptance
Monitoring and handover
Output weightLowMidHigh

The horizontal scale is stage order, not duration.

Timeline

What you get at each stage

The chart above is about weighting. This section is the physical version: what lands in your hands at the end of each stage, what we need from you, and roughly how long.

  1. 01

    Scope

    We write the problem and the scope into something you can sign: how the work actually runs today, which parts we are changing, and which parts we are not doing this time.

    We need someone on your side who can answer how it is actually done today.

    1–2 weeks
  2. 02

    Model

    The tables come first: which fields exist, how they relate, who is allowed to write. Screens and flows are settled in the same stage.

    We need you to confirm the field definitions and the exceptions: returns, exchanges, voids, credit notes.

    1–2 weeks
  3. 03

    Build

    Two weeks per increment, and each one ends with a preview URL you can click — not a written progress report.

    We need you to open the preview every two weeks and tell us what is wrong.

    4–10 weeks
  4. 04

    Launch

    Data migration, end-to-end tests for payments and e-invoicing in the production environment, a switchover runbook and rollback steps written down. Only then do we switch.

    We need your production keys and accounts, and people rostered for switchover day.

    1–2 weeks
  5. 05

    Run

    Three months alongside you after handover: fixes, adjustments, training. After that you can stay on maintenance, or hand the whole thing to your own engineers.

    Report a problem with the time it happened and a screenshot, and it saves a round trip.

    From 3 months

These are the common ranges estimated across the five stages, and they depend on scope. Website and e-commerce builds mostly land between 6 and 10 weeks, custom systems mostly between 3 and 6 months. The firm schedule comes at the end of the Scope stage, not as a number in the first meeting.

Stack & Why

Why this stack

Not because it is new, but because when something breaks you can find out why. What actually stalls a project in Taiwan is rarely the front end. It is payment callbacks, the invoice number ranges the tax office hands out each period, and deciding whose write wins when two machines sync.

  • Next.js · React · TypeScriptContent goes straight into the HTML, so Google and AI crawlers do not have to wait for JavaScript to finish before they can read it. Types stop half the field errors at compile time; testing only has to deal with the other half.
  • Supabase · PostgreSQLTables, permissions, files and scheduled jobs in one place. Permissions live in the database layer (row-level security), so no amount of front-end tampering gets around them — that is a different class of safety from a check written into the screen.
  • VercelEvery change gets its own preview URL, so you look at it before it goes live. If something does go wrong, rolling back is one button, not another deployment.
  • ECPay · PayUniThe ways Taiwanese buyers expect to pay — credit card, ATM transfer, convenience store code, mobile payment — are all behind these two. What actually goes wrong is idempotency on the callback: the same notification arriving twice must not be booked twice. We have walked into that one and fixed it.
  • 鯨躍 e-InvoiceIssuing, voiding and credit notes go through the API, so nobody has to log into a portal and type invoices by hand. Taiwan hands out invoice numbers in blocks each period; we walk you through that setup once at launch, and you renew it yourself after that.
  • LINE LoginThe reality of signing in in Taiwan. One less password to remember changes the sign-up completion rate, and when you later want to send a notification, the person is already on that channel.
  • Web Push · Google Calendar API · pg_cronThe things that should be remembered run on their own. The schedule runs on the database side, so it does not depend on one particular machine being switched on.

FAQ

What people ask before we start

These six come up most often on the first call. The answers are what we say on the phone; there is no second version.

What do we need to prepare before starting?
Three things: how it actually works today (Excel, paper and LINE groups all count), the three things you most want to change, and which third-party accounts have to be connected (payments, e-invoicing, LINE, the domain). You do not need a written specification to begin — producing one is what the Scope stage is for.
How long does a project take?
Website and e-commerce builds mostly land between 6 and 10 weeks. Custom systems depend on scope, commonly 3 to 6 months. The schedule turns on how large the scope is and how quickly you come back to us. We give a firm schedule at the end of the Scope stage, not a number in the first meeting.
Who maintains it after launch?
We stay with you for three months after handover, fixes and adjustments included. After that you can stay on maintenance, or take the source code and the database to your own engineers — the handover documents and the table descriptions were already delivered during the launch stage, so you are not tied to us.
Can we do only part of it?
Yes. A common one is the data model and the back office first, the front end later; or wiring payments and e-invoicing into the site you already have. What we do not take on is screens with no data work behind them — that usually just pushes the problem out by six months.
Can you work with the system we already have?
It depends on whether it will let the data out. If there is an API we connect to it; if it can only export CSV we set up a scheduled import; a completely closed cloud service needs a risk assessment before deciding whether to move off it. We have migrated a system of 7,181 records with nothing lost.
Do we have to meet in person?
No. Most projects run over online meetings, and we work with clients anywhere in Taiwan. When something has to be seen in person — how the POS at a counter actually gets pressed, for example — we come to the site.

Next Step

Start with where you are stuck

You do not need a specification first. If you can say which part no longer adds up, that is enough to start.

Talk about a project

Mind Information Technology Co.,Ltd. · Tax ID 91040213 · Established 2021 · 11F., No. 13, Ln. 332, Sec. 2, Zhongshan Rd., Zhonghe Dist., New Taipei City · +886 937 193 365

Contact