E-shop Launch Guide

• •Reads the .env.example file and tells you exactly which keys this shop needs and what each one is for.
• •Takes you through one service at a time and waits while you finish signing up.
• •Points out what is free and where you pay a commission or a monthly fee.
• •Helps with the choices signup asks about, such as the eu-central-1 (Frankfurt) database region for speed in Central Europe.

• •That you click through the signups yourself. The accounts are yours.
• •A confirmation after each service so it knows when to move on.
• •That you keep the copied keys aside for now. You enter them in chapter 6.

• •Creates the .env file with your keys. It stays on your computer and never reaches a code backup.
• •Generates a strong admin password and token so nothing stays at a default value.
• •Installs the dependencies and creates every table the shop needs in your empty database.
• •Starts the shop at http://localhost:3000 and leaves it running.

• •The keys you saved in chapter 5.
• •Your approval before it overwrites a file that already exists.
• •That you write down the admin password. You sign in with it at /admin/login.

• •Starts the local version at http://localhost:3000 and leaves it running, so changes show up in seconds.
• •Verifies before deployment that the shop builds without errors.
• •Tells you which database the project is currently pointed at, so you do not touch the live one by accident.

• •Your confirmation before it runs the build, because that also touches the database structure.
• •Your eyes. Look at the change in the browser before it goes out.

Only you can see it. For testing and edits.

• •Trying out new features
• •Design and content edits
• •Experimenting with no risk

Your customers see it. Live operation.

• •Real orders
• •Real payments
• •Real emails to customers

• •Checks that neither your keys nor your accounting documents end up in a public code repository.
• •Prepares the project for GitHub and pushes it there.
• •Lists exactly the variables this shop needs and says where each one comes from.
• •Checks after deployment that the public address really works.
• •Schedules the daily jobs (low-stock e-mail, review reminders, Google feed, cancelling unpaid card orders).

• •Signing in to GitHub and to Vercel. Both are done by you.
• •Entering the variables in Vercel. You type the keys in yourself.
• •Your approval before anything is made public for the first time.

• •Reads the events straight out of the shop's own code, so the list always matches your version.
• •Builds the exact webhook address from your domain.
• •Tells you where the signing secret belongs and why it also has to be in Vercel.
• •Walks a test order with you from cart to invoice.

• •Signing in to the Stripe dashboard and clicking the webhook together. That part is yours.
• •The copied whsec_ signing secret.
• •The decision on when to switch from test mode to live.

• •Updates the shop address inside the project, meaning .env and src/config/store.ts.
• •Reminds you of the places people forget: the Stripe webhook and the verified domain in Resend.
• •Gives you a closing list of what is finished and what is still waiting on you.

• •Buying the domain and having access to DNS at the registrar.
• •Entering the DNS records Vercel lists.
• •A little patience, DNS propagation is usually minutes, occasionally hours.

• •Replaces the default admin credentials with your own, both on your computer and in Vercel.
• •Fills in your company details in one place, which invoices, emails and the footer all read from.
• •Walks you through the VAT setting in the admin (Nastavení › DPH), which invoices, e-mails and the accounting agent in chapter 12 all read.
• •Goes through the Ready to launch checklist in the admin with you, so nothing is forgotten.

• •Your real company details, company number, VAT number and bank account.
• •That you save the new admin password. You sign in with it at /admin/login.
• •A deployment, so the new values reach the live address too.

• •Takes your issued invoices and credit notes straight from your shop's database.
• •Reads the received invoices from your folder, even if they sit in subfolders or appear twice.
• •Has two independent auditors check duplicates, documents issued to someone else, EU reverse charge, credit notes and documents from the wrong month.
• •Generates the DP3, KH and SHV XML and validates it against the tax authority's schemas.

• •A folder with the received invoices for that month, however loosely dumped in.
• •Decisions on borderline documents. The agent presents and explains them, you decide.
• •Uploading the finished XML to mojedane.cz. Filing is always done by the taxpayer.

• •Answers customers in the shop's language (Czech or English): where is my order, withdrawals, complaints, cancellations, e-mail changes.
• •Every reply is checked by code and by a second agent before it goes out: no invented amounts, dates or promises.
• •Starts in trial mode: replies wait for your approval, and you switch it live once you are happy.
• •After every run it sends you a summary of what went out and what waits for you.

• •Approvals, edits and exceptions in the admin (Čeká na vás).
• •Refunds: support never sends money; you refund the customer yourself and click Vráceno in the admin.

• •Asks about your program and its edition, the warehouse, a physical store, and what should be booked in the program.
• •Checks your product codes: what has no code and which codes are on two items. It fills in the missing ones from your program or by EAN.
• •For POHODA and Money S3 it walks you through installing a small helper on the accounting PC. That is one line pasted into PowerShell, no administrator rights needed.
• •For Dotykačka it sets up the ready translator. For other cloud systems it reads the vendor's official documentation, then writes and tests the translator.
• •Goes through the trial preview with you: how many items were matched and what would drop to zero.
• •Writes down in the shop's notes how the stock is connected, so every later Claude Code session knows.

• •A few clicks in the admin: Stock › Connections › “New connection”.
• •Your POHODA or Money password, typed only on the accounting PC. It never goes into the chat.
• •For a cloud system, access to its API, which you create with the vendor and enter into the shop's settings yourself.
• •Pressing “Switch to live”. Claude never does that for you.

• •A stock list is refused when over half of the goods in stock would drop to zero, when it is much shorter than the last one, or when too few items match. Nothing changes and the admin says why. “Apply anyway” is your call alone.
• •Only quantities change. The connection never creates, hides, deletes or reprices a product.
• •A web order placed in the middle of a sync is never lost or counted twice.
• •A web sale that the program has not booked within 14 days stops being subtracted, so the numbers cannot drift.
• •The helper on the POHODA PC can only read stock and add issue and receipt notes. It never deletes or changes anything in POHODA.
• •Accounting passwords stay on the accounting PC only, encrypted for your Windows account.

• •The POHODA or Money PC has to be on and logged in during the day. While it is off, the shop sells from the last known numbers and everything catches up once it is back.
• •Do you also sell from the same stock in a physical store? Now and then the last piece can sell on the web and at the till at the same moment. Keeping a few pieces back for the store helps, and the admin shows you any oversold item.
• •Your program's licences (POHODA edition, Money module, Dotykačka plan) are yours, paid to its vendor. The connection itself is part of the shop.
• •Have your accountant confirm what should be booked. If you turn on booking the shop's invoices and credit notes in Money, they go into Money by themselves, so do not create them there by hand any more. Without that option you keep moving them with the monthly export or by hand.

• •Asks which supplier it is, what you want to sell from them and where your shop runs.
• •Reads the supplier's whole file and shows what the shop takes from it: prices, stock, photos, categories and variants.
• •If the supplier has a format of its own, writes a short description for it, tests it on the whole file and deploys the shop so it knows the description.
• •Proposes a price rule and shows it on real goods: the cheapest, the most expensive and the items the minimum margin lifts.
• •Turns the supplier's hundreds of categories and filters into a clear category tree with your own names.
• •Walks you through the trial preview, then photos and supplier stock, and records in the shop's notes how the supplier is connected.

• •The address of the supplier's file, entered only in the admin ("New source").
• •Your margin: a markup in percent and the lowest margin you are willing to sell at.
• •Which of the supplier's categories you want to sell and what they should be called in your shop.
• •Pressing "Go live" and showing the new products. Claude never does that for you.

• •A cut-off or damaged file is refused as a whole: "The file is cut short, its end is missing. Nothing was changed."
• •If the file holds over a fifth fewer goods than last time, the run stops and waits for you.
• •Goods that disappear from the file are sold out only after two complete runs, and hidden after 30 days. They come back by themselves when the supplier lists them again. Nothing is deleted. When a lot disappears at once, you decide.
• •A price that drops below half or rises by over half is held. When many prices change at once, all of them are held and wait for you.
• •A held price never sells at a loss: if the old price is now below cost plus the minimum margin, the product waits for "Approve price".
• •Without an approved trial, one run adds at most 300 new products.
• •Texts, photos and prices you edit are never overwritten by the supplier, and a product you delete is never created again.
• •The same goods are never created twice, not even from two suppliers. Goods you already have in the shop are offered for pairing in the trial.

• •The shop downloads photos once, makes them smaller (about 120 kB a photo) and stores them in your own storage: Cloudflare R2, Vercel Blob or your server's disk. 10,000 products with 5 photos each come to about 6 GB, which fits in R2's free 10 GB. Downloading thousands of photos takes hours; the trial tells you how many. The storage is part of your hosting, not a fee for the shop.
• •Database: the trial tells you up front how much it grows. Free database plans are usually around 0.5 GB; for a big catalogue you pick a larger plan with your database provider.
• •One VAT rate: the shop works with one VAT rate so that every invoice is right. In a VAT payer's shop, goods at another rate are not created and are listed separately. Want to sell them? Claude Code sets up the other rate in the shop: the admin offers you the request for it right next to those goods.
• •Texts arrive in the supplier's language. On request Claude Code translates them or rewrites them in your own words with you, in batches, which also helps in search engines.
• •Goods the supplier ships can, now and then, sell just as the supplier runs out. A stock reserve in the stock settings helps, and an order for goods the supplier withdrew shows up in Orders › Needs attention.
• •The shop does not show the supplier's crossed-out "recommended price": under EU rules a crossed-out price must refer to the lowest price of the last 30 days. You run a sale with your own price.