The step most global Shopify guides skip entirely
Most Shopify setup guides are written for markets where Shopify Payments works out of the box, connect your bank details, accept cards, done. South Africa is not one of those markets. Shopify Payments does not support South African merchant accounts, so the very first meaningful decision in a local Shopify setup is which third-party gateway to connect, and that single difference changes several other steps that follow it.
This checklist assumes you have already chosen your plan and theme direction. It focuses on the sequence that actually matters for a South African launch: payments and tax first, because they affect financial and legal correctness; shipping and apps next, because they affect the customer experience; domain, email and SEO basics after that, because they affect how credible and discoverable the store is from day one; then a genuine test order before you tell anyone the store is live.
Skipping the order matters more than skipping any single step. A store with a beautiful theme and an unconfigured tax setting, or a working gateway nobody has actually tested end to end, will cost you more in refunds, disputes and lost trust than a plainer store that got the sequence right.
Step 1, payments, the South African way
| Task | Why it matters here specifically |
|---|---|
| Choose a third-party gateway | Shopify Payments is unavailable in SA, PayFast, Yoco and Peach Payments are common, established choices |
| Get a current, written fee quote from your chosen gateway | Published rate cards change and can vary by volume, confirm your actual number before pricing products |
| Understand Shopify’s additional third-party transaction fee | This stacks on top of your gateway fee purely because you are not using Shopify Payments, budget for both |
| Confirm supported payment methods match your customers | Card, instant EFT and popular local wallets vary in support by gateway, check against your actual audience |
| Complete a full test transaction, including a refund | A gateway that "connects" is not the same as a gateway that has been proven to actually process and refund correctly |
Step 2, tax and VAT, set correctly before your first sale
Configure your tax settings based on your actual VAT registration status before your store processes a single real order. A store that launches with default or incorrect tax settings often does not notice the problem until an accountant reviews the first quarter’s numbers, by which point every affected order needs manual correction.
If you are VAT registered, confirm Shopify is calculating and displaying VAT correctly on both the product page and the checkout, and that your invoices reflect it properly for customers who need one for their own accounting. If you are not yet VAT registered, confirm your settings reflect that too, since displaying tax incorrectly in either direction creates real accounting and customer-trust problems.
This is a genuinely easy step to get right at setup and a genuinely painful one to fix retroactively across historical orders. Involve your accountant or bookkeeper in this specific step before launch, even if they are not involved in the rest of the build, and confirm they have actually reviewed the live checkout, not just a settings screenshot.
Step 3, shipping zones and couriers that match SA reality
- Set shipping zones around real delivery capabilityMetro, regional and remote-area delivery times and costs genuinely differ across South Africa, do not default to a single flat national rate without checking it against real courier quotes.
- Connect a courier your fulfilment can actually supportConfirm collection times, tracking integration and how failed or delayed deliveries are handled before committing to one provider.
- Decide on a free-shipping threshold deliberatelyModel the margin impact honestly rather than copying a competitor’s threshold without checking your own average order value and shipping cost.
- Set clear delivery estimate messagingSouth African shoppers are sensitive to vague delivery promises, a specific, honest estimate range builds more trust than an optimistic generic one.
- Test the shipping calculation at checkoutRun a real test order to confirm the displayed shipping cost matches what you will actually be charged by your courier.
Step 4, apps: add deliberately, not by default
Every app added to a Shopify store carries three costs: its subscription fee, a small amount of page-load weight, and a new point where checkout could break if the app updates badly or conflicts with another. Before installing anything, ask what specific problem it solves that your theme and Shopify’s native features genuinely cannot handle on their own.
A lean starting stack typically covers reviews, basic email marketing or abandoned cart recovery, and possibly a specific inventory or accounting integration your business genuinely needs. Resist the instinct to install every app a "best Shopify apps" list recommends, a smaller, well-understood app stack is easier to maintain, debug and keep fast than a large one nobody fully remembers installing.
Review your installed apps every few months and remove anything no longer earning its place. App subscriptions are one of the easiest costs to let quietly accumulate on a Shopify store, and an unused app can still slow down your storefront even while producing zero value.
Step 5, before you announce the launch
- A complete test order placed as a real customer would, from product page through to confirmation email
- A test refund processed and confirmed through your actual gateway
- Mobile checkout tested specifically, most South African ecommerce traffic arrives on a phone
- Order confirmation and shipping notification emails reviewed for accuracy and tone
- Analytics and conversion tracking (GA4, and any ad platform pixels) verified as firing correctly
- A clear, visible way to contact support, WhatsApp click-to-chat performs especially well for SA shoppers
- Returns and refund policy pages written in plain language and genuinely linked from checkout, not just buried in a footer
A Shopify store is not launch-ready because the theme looks finished. It is launch-ready when a stranger can complete a real purchase, get a real refund, and reach a real person if something goes wrong, and you have actually watched all three happen.
Jordan Blake, Web & Conversion Strategist
A worked scenario: the launch that nearly shipped with the wrong fee assumption
A homeware brand preparing to launch on Shopify had priced its entire catalogue assuming only a single gateway fee, having found one confident number in an old blog post during research. During our pre-launch review, we confirmed the current gateway rate directly with the provider and flagged Shopify’s additional third-party transaction fee, which the brand had not accounted for at all.
The combined, corrected fee stack was meaningfully higher than the single number they had planned around. Because this surfaced before launch rather than after three months of live sales, the brand adjusted a handful of thinner-margin product prices and avoided discovering the gap only once real orders (and real, smaller-than-expected margins) had already been processed.
This is exactly the kind of setup step that is invisible until it is expensive. Confirming your real, combined fee stack before finalising prices belongs firmly inside the setup checklist, not treated as a separate finance task to handle "at some point" after launch.
Domain, email and the small details that undermine credibility
A store still running on a default Shopify subdomain at launch, with no custom domain connected, quietly signals an unfinished build to a first-time visitor, even if every other part of the setup is complete and well-configured. Connect and properly propagate a custom domain before announcing the launch, and confirm SSL is active so the address bar shows a secure padlock rather than a warning.
Set up a professional email address on your own domain for order confirmations and support replies, rather than leaving Shopify’s default sending address or a personal Gmail account as the customer-facing point of contact. This is a small, cheap detail that meaningfully affects how trustworthy the entire store feels to a cautious first-time buyer checking who they are actually paying.
Also review your legal pages (returns policy, terms of service, privacy policy) before launch rather than relying on generic template text nobody has actually read against South African consumer protection expectations. These pages rarely get visited by most customers, but the small number who do check them before a first purchase are often your most cautious, highest-value buyers.
Step 6, SEO and analytics basics before launch
| Task | Why it matters at setup, not later |
|---|---|
| Connect GA4 and Google Search Console | Early data collection means you have a real baseline the moment marketing spend begins |
| Set clear, descriptive product titles and meta descriptions | Retrofitting hundreds of products later is far slower than setting a naming convention from the start |
| Confirm collection and product URLs are clean and stable | Changing URL structures after launch creates redirect work and can disrupt early search indexing |
| Set up conversion tracking for ad platforms you plan to use | Untracked early campaigns waste budget on data you can never recover retroactively |
What to do next
Work through payments and tax first, they are the two steps most likely to create real financial or legal problems if skipped, and both are genuinely fast to get right when tackled deliberately at the start rather than retrofitted later.
Once payments, tax and shipping are configured, resist rushing straight to launch. Run the full test-order-and-refund sequence, check mobile checkout specifically, and confirm your analytics are actually tracking before you tell a single customer the store is open.
Nexus builds and configures Shopify stores for South African merchants, including gateway setup, tax configuration and a full pre-launch QA pass, read our Shopify vs WooCommerce guide next if you have not yet committed to a platform.
.png){kind=spacer}
 Which Store Platform Wins.png)
