Start with the pages every site should have
A new website should not go live with only a homepage and a contact form. If the site collects names, messages, delivery details, payment information or booking details, you need clear documents that explain what happens to that information and how the site is used. For South African businesses, that usually means Terms and Conditions, a Privacy Policy and, where relevant, cookie and consent notices, refund wording and supplier or booking terms.
The aim is simple: visitors should not have to guess. If your business sells online, offers appointments, runs subscriptions or takes enquiries through a form, the legal wording must reflect those steps exactly. A page that says one thing while the checkout or booking flow does another creates confusion and risk.
Before launch, check that each page answers the basics:
- Who is running the website and how customers can reach the business through the contact page
- What personal information is collected and why it is needed
- How payments, cancellations, refunds and delivery are handled
- What the business will do if a customer breaks the site rules or abuses the platform
Match the documents to the actual user journey
Many launch problems come from documents that are too generic. A brochure site for a consultancy does not need the same wording as a shop that ships parcels across the country or a booking platform that sends reminders and collects deposits. If the process changes, the documents must change too.
At TsAndCs, the review usually starts with the user journey. That means looking at what happens from the first click to the final confirmation. Where are forms used? Is there an account login? Are there recurring charges? Is the customer choosing a service date? Each of those steps can trigger a different clause or disclosure. A business in Gardens may have local walk-in customers and nationwide online clients, so the wording needs to cover both fairly and clearly.
Common items that need review before launch include:
- Quote request forms and callback forms
- Checkout pages, basket rules and payment confirmation text
- Booking calendars, cancellation windows and no-show rules
- Newsletter opt-ins and promotional consent wording
- Pop-ups, tracking notices and data sharing statements
Check POPIA details before the first form is published
If the website collects personal information, the privacy wording must make sense under POPIA. That does not only mean the privacy policy itself. It also includes the wording on contact forms, account creation pages, lead forms and any consent tick-boxes. If a form is too vague, the visitor cannot give proper informed consent and that is where trouble starts.
Make sure the form explains why the information is needed, how long it will be kept, who may receive it and what happens if the user does not submit the required fields. If you share information with couriers, payment processors or message service providers, that should be reflected in the policy and the internal process. For businesses in coastal areas like Sea Point, humidity and load-shedding may affect server reliability and backup routines, so it is also worth checking how form submissions are stored and recovered if there is an outage.
A useful pre-launch POPIA check is to ask three questions:
- Are we collecting only what we actually need?
- Is the reason for collection clear on the page itself?
- Can we explain where the information goes and who sees it?
Don’t let ecommerce and booking rules fight each other
Ecommerce sites and booking sites often need different legal logic. A store may need delivery cut-offs, out-of-stock wording and return rules, while a booking business needs rescheduling terms, deposits, service restrictions and site-specific conduct rules. If both systems sit on the same website, the documents should not contradict each other.
This matters more than many owners realise. A customer who books a service in Claremont, for example, may expect one set of rules for cancellations and another for a product delivery order. If the language is mixed up, staff spend more time resolving disputes and the customer experience suffers. Clear setup from the start is less work than trying to fix complaints later.
Before launch, confirm whether the site needs any of these:
- Subscription terms for repeat billing or monthly services
- Delivery zones, lead times and collection wording
- Minimum notice periods for cancellations or changes
- Age restrictions or service exclusions
- Special instructions for high-risk products or time-sensitive orders
Add disclosures where a customer might miss them
Some disclosures are not full policy pages but they still matter. If a site uses cookies, analytics or remarketing tools, the visitor should know. If content is promotional, sponsored or tied to an incentive, that should be made clear. If the business relies on third-party platforms for payment, bookings or messaging, the customer should not be left guessing about who is handling what.
Good disclosure placement is practical, not noisy. Put the important points near the action, not hidden in a footer that no one reads. That can include a short notice below a contact form, a summary above the payment button or a link next to a consent tick-box. A launch review should also check whether the wording is readable on mobile, since many customers will visit the site from their phones on the go or on unstable connections.
When reviewing disclosures, ask whether a first-time user would understand:
- What they are agreeing to before they click submit
- Whether the business uses tracking or automated follow-up
- Which pages carry binding terms and which are just information
Use a local example to test the full launch pack
Take a small Cape Town service business based in Gardens that offers online quotes, in-person appointments and monthly support packages. Before launch, the site should not only have a Privacy Policy and Terms and Conditions. It should also have form wording for quote requests, a clear booking policy, a subscription clause if recurring services are sold, and a simple cancellation notice that staff can point to when a client asks questions.
That same business may serve customers in the CBD, Bellville, Stellenbosch and Paarl, so the wording must work for both local and nationwide users. If the business has a walk-in office and an online intake form, the legal setup should treat both channels properly. One page should not promise in-person service rules while another page assumes the customer only deals online. It sounds small, but these mismatches cause delays and complaints.
A final launch check should confirm the basics are in place:
- All policy links are live and easy to find
- Form wording matches the privacy policy and consent settings
- Refund, cancellation and delivery terms are consistent
- Contact and support details are accurate
- The team knows which document to use when handling customer queries
Make compliance part of the launch process, not a clean-up job
The best time to sort website compliance is before the first customer arrives. Once the site is live, every form submission, order and booking creates an expectation that the rules are in place and working. A launch-ready document pack gives the business a clear structure and helps the team respond consistently when questions come in.
For businesses that want a practical rollout, TsAndCs supports policy pack customisation, compliance review, privacy gap analysis, POPIA alignment, PAIA support, ecommerce policy setup, booking site documents, subscription policy support, platform terms drafting, policy updates, launch readiness checks and ongoing compliance support. The point is to make the legal side fit the way the business actually operates, not the other way round.
If the documents are checked early, the launch is calmer, the team has less back-and-forth and the website starts with the right paperwork in place. That saves time now and avoids a mess later.
