GoHighLevel Ecommerce Store: Setup & Fees (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 13 August 2026 · 8 min read

A GoHighLevel ecommerce store is a genuinely capable way to sell digital products, services, courses and small physical ranges — provided you accept that it is a checkout and automation engine first, and a product catalogue second. Everything lives under Payments in the sub-account, the storefront renders as a page inside the funnel or website builder, and Stripe does the actual money movement. If you sell fewer than roughly fifty SKUs, do not need live carrier rates, and care more about what happens after the sale than about merchandising, it will do the job well.

What follows is the build sequence I use with Australian clients, the fee structure you actually need to understand before you quote a client, the GST and shipping realities, and the point at which I tell people to stop fighting the platform and put their catalogue on Shopify instead. I have built these for physiotherapy clinics selling rehab equipment, consultants selling templates, and coaches bundling digital downloads with 1:1 time — the answer changes depending on which of those you are.

Where the store actually lives in GoHighLevel

The single biggest source of confusion for new admins is that there is no menu item called "Store" at the top level. The pieces are scattered across three places, and you need all three configured before a customer can buy anything.

Payments > Products

This is your product database. Every product you create here — digital, physical, service, one-time or recurring — becomes available to Order Forms, the store page, invoices, and the mobile app. Products carry a name, description, media gallery, product type, and one or more prices. A product with three prices (monthly, annual, lifetime) is still one product; the prices are child records. This matters because the store page displays the product and lets the buyer pick the price, whereas an Order Form is usually pinned to a single price.

Payments > Settings and Store settings

Under Payments you connect your payment provider, set the currency for the sub-account, configure tax rates, and manage the store-specific settings: store name, the URL slug, contact email, and which funnel or website page acts as the storefront. Currency is set once per sub-account and is painful to change later, so set AUD before you create a single product.

The store page inside Sites > Funnels or Websites

The storefront itself is a page you build in the drag-and-drop builder. You add the Product List element to display a catalogue or a chosen collection, the Product Detail element on a dedicated product page, and the Shopping Cart element in the header so buyers can see what they have added. Checkout is a separate step handled by GoHighLevel. In practice I build three pages inside one funnel: shop, product detail, and thank-you. The thank-you page is the trigger point for everything downstream.

Creating products, prices and variants

Create the product before you build a single page. Retrofitting products into an existing design always costs more time than doing it in order.

Product type and media

Choose the product type honestly — digital, physical or service. Digital products let you attach a downloadable file that is delivered automatically after payment, which removes an entire workflow you would otherwise have to build. Physical products expose shipping and inventory fields. Service products suit consultations, installs and anything you fulfil manually. Upload at least three images per product; the Product List element crops to a square by default, so square source images at around 1000 x 1000 pixels avoid the awkward head-chopping you get from landscape photos.

One-time versus recurring prices

A one-time price charges once. A recurring price creates a Stripe subscription with your chosen interval, and optionally a setup fee and a trial period. Recurring prices are where the GoHighLevel store earns its keep for service businesses: a $290 per month retainer, a $49 per month member plan, or a $1,500 setup plus $500 monthly, all handled with the same product record. If you are selling ongoing access to content rather than a product, look at whether a membership offer is the better vehicle — my GoHighLevel memberships and courses setup guide covers when to sell through the store versus through Memberships, and how to link the two so one purchase grants access.

Variants

Variants handle size, colour, format and similar options. You define variant groups and options on the product, then generate the combinations. Be realistic here: variants in GoHighLevel are workable for a t-shirt in four sizes and two colours. They become unpleasant at forty combinations, and they do not carry independent images per variant as cleanly as a dedicated ecommerce platform does. If your catalogue is variant-heavy, that is your first serious signal that you are on the wrong tool.

Collections, store pages and the shopping cart

Collections group products for display — "Rehab Equipment", "Digital Downloads", "Starter Bundles". A product can sit in multiple collections. On the page, the Product List element can be pointed at all products or at a specific collection, which is how you build category pages without any custom code.

The Shopping Cart element is a small but important detail. Without it on the page, a buyer who adds two items has no visible way to review the cart before checkout. I place it in the header section of the store funnel and set it to sticky on desktop. Test the full path on a real phone, not just the builder preview — cart icons frequently collide with mobile menu icons in stock templates.

One structural decision worth making early: whether you want a browsable store at all. Plenty of the highest-converting builds I have done skip the store page entirely and drive traffic straight to Order Forms inside funnels, using the Products database purely as the price source. If your offer is one flagship product plus an upsell, that is almost always the better route.

Connecting Stripe and PayPal

Stripe is the primary integration and the one I recommend for every Australian sub-account. Connect it under Payments > Integrations using the Connect flow, which links your existing Stripe account rather than creating a new one. Once connected, run a live test transaction for a small amount and refund it — test mode does not surface every real-world issue, particularly around 3D Secure prompts on Australian cards.

PayPal can be connected as an additional option and is worth enabling if your audience skews older or consumer, where PayPal balances and PayPal-stored cards genuinely lift conversion. It is more limited than Stripe for recurring billing and does not support every GoHighLevel payment surface, so treat Stripe as the backbone and PayPal as a secondary button on one-time purchases. Detailed connection steps and troubleshooting sit in the GoHighLevel help documentation.

Reconciliation

Money landing in Stripe is not the same as money reconciled in your books. Stripe payouts arrive as batched lump sums with fees netted off, which does not match invoice-by-invoice records. If your bookkeeper is chasing you at the end of every quarter, the GoHighLevel Xero integration is the piece that closes that loop and stops manual re-keying of every order.

Transaction fees and who pays what

There are two layers of cost, and conflating them is how agencies end up quoting margins that do not exist.

The first layer is the payment processor. Stripe charges a percentage plus a fixed amount per successful card charge in Australia, with a higher rate on international cards and an additional currency conversion component where relevant. Chargebacks and disputes carry their own fee. These rates change, so check the current schedule on the Stripe Australia pricing page rather than trusting a number in any blog post, including this one. PayPal's structure is similar in shape but different in the specifics.

The second layer is the platform. GoHighLevel's own treatment of transaction charges depends on your agency plan and how payments are configured — some plan tiers and payment routes carry an additional platform charge on transactions processed through the system, and this has changed more than once. Before you build a client's revenue model on it, log in to your agency account and read the current terms in your own billing settings. That is the only source that reflects your actual arrangement.

Who pays what is a business decision, not a technical one. Australian consumer law is unforgiving about surprise surcharges, so if you intend to pass processing costs to the buyer, disclose it plainly at checkout and keep it to genuine cost recovery. For B2B service businesses I generally advise absorbing the fee and building it into the price, because a 1.75% line item at checkout costs more in abandoned carts than it saves.

GST, tax settings, shipping and fulfilment

GST for Australian sellers

Under Payments > Settings you can create tax rates and apply them to products. For a GST-registered Australian business selling domestically, that is a 10% rate applied to taxable products, and you need to decide whether prices are tax-inclusive or tax-exclusive. Australian consumers expect displayed prices to include GST, so tax-inclusive display is almost always correct for B2C. GST-free items — certain health services, some food, exports — need their own rate of zero rather than simply having no tax applied, so the exemption is visible in your records. Check the treatment of your specific products with your accountant; the platform will do exactly what you configure and nothing more.

Shipping

This is the honest weak point. Shipping in the GoHighLevel store is basic: flat rates, simple rules, and no live carrier calculation from Australia Post or StarTrack. There is no dimensional weight logic, no zone-based table rate engine of any sophistication, and no native label printing. If you ship a handful of light, uniformly sized items nationally at a flat $12.95, it works fine. If you ship bulky goods where freight varies from $9 to $90 depending on postcode and weight, you will either lose money or over-charge customers.

Inventory

Inventory tracking exists at a basic level — you can set available quantity and have products show as out of stock. There is no multi-location stock, no purchase order handling, no supplier management, and no sync with a warehouse system or point-of-sale. Businesses running a physical shopfront alongside an online store should not attempt to run stock control here.

Order confirmations and post-purchase automation

This is where a HighLevel ecommerce store beats a standalone cart platform, because the automation layer is not an add-on you pay extra for.

The confirmation sequence

Build a Workflow with an order-submitted or payment-received trigger, filtered by product where you need different messages per product. From there: send the receipt email, deliver the digital file or membership access, add a tag such as customer-rehab-kit, create an opportunity in the fulfilment pipeline if a human needs to act, and send an internal notification. Use custom values for the business name, support email and ABN so the same template works across sub-accounts without editing.

Receipts only help if they arrive. Purchase confirmations are transactional and highly monitored by inbox providers, so a poorly authenticated sending domain will damage both deliverability and trust. Work through GoHighLevel email deliverability and Mailgun setup before launch, not after the first customer says their receipt never arrived.

Abandoned cart and follow-up

Trigger an abandoned-checkout workflow when a buyer reaches the checkout and does not complete payment. Two emails and one SMS over 24 hours recovers a meaningful share of orders for most of my clients — the first message within an hour, framed as a helpful nudge rather than a discount. Save discounting for the third touch, if at all. Post-purchase, use one-click upsells on the thank-you step and a review request seven days later.

Higher-value sales

Not every sale should go through a cart. Once you are past roughly $3,000, or the scope needs negotiating, a quote document converts better than a checkout button. GoHighLevel proposals and estimates handle that path with signatures and deposits, and still feed the same pipelines and workflows.

GoHighLevel ecommerce store versus Shopify and WooCommerce

I have no interest in pretending the platform does something it does not. Here is how I compare them when scoping a build.

My rule of thumb: if the sale is the beginning of a relationship, build it in GoHighLevel, because the follow-up is where the value sits. If the sale is a transaction in a catalogue of physical goods, use Shopify and push the customer record back into GoHighLevel for marketing. Whichever way you go, make sure revenue actually appears in your reporting — GoHighLevel dashboards and reporting will show product revenue and conversion only if orders are attributed properly from the start.

Common mistakes to avoid

• Setting the sub-account currency to USD by habit, then discovering after twenty products that Australian customers are being charged in the wrong currency and copping conversion costs.
• Building the storefront pages before creating products, which forces a rebuild of every element once the real product records exist.
• Quoting a client on transaction margins using percentages found in a blog post rather than the current Stripe schedule and their own agency billing terms.
• Configuring GST-free items by leaving tax off entirely instead of applying a zero-rated tax, which makes BAS preparation guesswork.
• Promising live Australia Post rates and postcode-based freight because nobody checked the shipping settings before the proposal was signed.
• Launching without a real end-to-end test purchase on a phone — including receipt delivery, digital file access and the abandoned cart trigger — and finding out from the first customer.

If you want your GoHighLevel store, payment flows and post-purchase automations built properly the first time, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Can a GoHighLevel ecommerce store handle physical products with shipping?

Yes, but only simply. You can mark products as physical, set stock quantities, and charge flat or rule-based shipping rates. There is no live Australia Post or courier rate calculation, no dimensional weight logic, and no label printing. It suits light, uniformly sized items shipped at a flat rate. Bulky or variable freight needs Shopify or WooCommerce.

What does it cost to sell through the GoHighLevel store?

There are two cost layers. Stripe or PayPal charge their standard processing fees on each successful transaction, with higher rates on international cards. Separately, GoHighLevel may apply platform conditions on transactions depending on your agency plan and payment configuration. Check the current Stripe Australia pricing page and your own agency billing settings, as both change over time.

Do I need to charge GST on products sold through the store?

If your business is registered for GST and the product is taxable, yes. Create a 10% tax rate under Payments settings and apply it to the relevant products, choosing tax-inclusive display for Australian consumers. GST-free items should be given a zero-rated tax rather than no tax at all, so the exemption is recorded. Confirm the treatment of your specific products with your accountant.

Can I sell subscriptions as well as one-time purchases?

Yes. A single product can carry multiple prices, including recurring prices with your chosen billing interval, an optional setup fee and a trial period. Recurring prices create Stripe subscriptions, and failed payments can trigger Workflows for dunning emails and SMS. This is one of the strongest reasons service businesses choose the built-in store over an external cart.

Should I use the store page or send traffic straight to an Order Form?

If you sell one or two flagship offers, send traffic straight to an Order Form inside a funnel and use the Products database purely as the price source. Conversion is almost always higher without a browsing step. Build a full store page when you genuinely have a catalogue customers need to browse and compare across collections.

Related articles

• GoHighLevel order forms and upsells
• GoHighLevel Stripe integration
• GoHighLevel abandoned cart recovery
• GoHighLevel funnel builder