E-commerce Stores

Native Dynamic E-Commerce Analytics, Product Reporting & Comprehensive E-Commerce Training
FEATURE REQUEST: NATIVE DYNAMIC E-COMMERCE ANALYTICS & REPORTING HighLevel should prioritize the development of a comprehensive native e-commerce analytics and reporting system. HighLevel already captures substantial commerce data within Orders, Transactions, Products, Customers, and Order Line Items. However, e-commerce operators need a native analytical layer that can aggregate, filter, compare, and visualize this information without requiring complex Opportunities, Pipelines, Workflows, Custom Fields, APIs, manual exports, external databases, or third-party business intelligence tools. At a minimum, an E-Commerce Analytics Dashboard should provide: FINANCIAL REPORTING • Total revenue • Gross product revenue • Net revenue • Total orders • Average order value • Tax collected • Shipping revenue • Discounts • Additional charges and fees • Refunds and partial refunds • Revenue after refunds PRODUCT REPORTING • Total units sold • Quantity sold by product • Quantity sold by variant • Revenue by product • Revenue by variant • Best-selling products by quantity • Best-selling products by revenue CATEGORY & COLLECTION REPORTING • Units sold by category or collection • Revenue by category or collection • Category performance over time CUSTOMER REPORTING • Total unique customers • New customers • Repeat customers • Repeat purchase rate • Orders per customer • Revenue per customer • Customer lifetime value • First purchase date • Last purchase date • High-value customer identification BASKET, ADD-ON & UPSELL REPORTING • Products purchased together • Average items per order • Add-on units sold • Add-on revenue • Add-on attachment rate • Upsell performance • Cross-sell performance ATTRIBUTION REPORTING • Revenue by source • Revenue by channel • Revenue by campaign • Revenue by UTM parameters • Revenue from email • Revenue from SMS • Revenue from social media • Revenue from affiliates and vendors DYNAMIC DASHBOARD CAPABILITIES Users should be able to: • Select custom date ranges • Compare reporting periods • Filter by product • Filter by variant • Filter by category • Filter by customer type • Filter by source and campaign • Create charts and tables • Export reports • Schedule recurring reports WHY THIS MATTERS Opportunities and Pipelines are extremely valuable for CRM, sales, customer journey, and operational tracking. However, they should not be required as a workaround for foundational e-commerce reporting. A business owner should be able to open an E-Commerce Analytics Dashboard and immediately answer: What did I sell? How many did I sell? How much revenue did each product generate? Which categories are performing? How much tax did I collect? What was refunded? Who are my new and repeat customers? What is my customer lifetime value? Where is my revenue coming from? Which products, customers, and campaigns are driving my business? HighLevel has an enormous competitive opportunity. The platform already connects: TRAFFIC → MARKETING → CRM → CONTACT → CUSTOMER → PURCHASE → AUTOMATION → RETENTION Adding comprehensive native commerce analytics would complete the ecosystem: TRAFFIC → MARKETING → CRM → CONTACT → CUSTOMER → PURCHASE → PRODUCT → REVENUE → RETENTION → REPORTING ADDITIONAL REQUEST: COMPREHENSIVE E-COMMERCE TRAINING HighLevel should also develop a comprehensive, official, start-to-finish e-commerce video training program. The training should accommodate auditory, visual, and hands-on learners and cover the complete process of: • Store setup • Products and variants • Categories and collections • Payments • Taxes • Shipping • Orders • Transactions • Refunds • Workflows • Opportunities and Pipelines • Attribution • Dashboards • Reporting • Testing • Troubleshooting • Scaling HighLevel has built an exceptionally powerful CRM, automation, and marketing ecosystem. Native dynamic e-commerce analytics and comprehensive e-commerce training would eliminate a significant barrier for business owners who want to operate their entire business within HighLevel. Please prioritize this development.
0
Add Collections and Cost/Margin to the Product CSV Import (make bulk import truly bulk)
The problem The "Import products by CSV" tool is genuinely great, and for anyone loading a real catalog it is the difference between minutes and hours. It already imports Title, Description (Body HTML), Handle, Variant Price, Compare-at Price, Track Inventory, Available Quantity, SKU, Weight, Dimensions, Product Labels, and both SEO Title and SEO Description. That is almost the entire product form. But it is missing two fields that nearly every product needs: Product Collection and Cost Price / Margin. Because those two are not in the CSV, every imported product still has to be opened one at a time to assign its collection and enter its cost. On a 30-product catalog that is 30 manual passes after the "bulk" import, which defeats the purpose of importing in bulk in the first place. What we are asking for Add columns to the import CSV for: Collection(s) (comma-separated, matched by name, created if it does not exist) so products land in the correct store category on import. Cost Price and Margin so profit tracking is populated from the start instead of left blank. Every one of these already exists in the manual product form. This is about bringing the CSV up to parity with the form, not building anything new. Why it matters Agencies onboard clients by loading an entire catalog at once. Every field the CSV cannot carry becomes a manual, per-product step that scales linearly with catalog size and eats the exact time savings the importer is supposed to deliver. Collections and cost are not edge cases. They are on almost every product. Completing the CSV turns a strong feature into a true one-click catalog load and makes GHL a serious option for stores with real inventory. Thank You for taking the time to consider this. Keep up the good work. Thanks
0
URGENT: Add Customer Phone Number to Packing Slips for eCommerce Order Fulfillment
This is a business-critical requirement for every eCommerce store using HighLevel. Currently, packing slips do not support displaying the customer's phone number. This creates serious operational issues during order fulfillment and delivery. Real-world delivery scenarios happen every day: • Customer is not opening the door • Address is difficult to locate • Building, apartment, or society gate is locked • Delivery agent needs delivery confirmation • Customer entered incomplete address details In all of these cases, the customer's phone number is often the only way to complete a successful delivery. After discussing this with HighLevel Support, it was confirmed that: • Customer phone numbers are not supported on packing slips • No workaround currently exists • No alternative workflow exists • No documentation exists explaining how merchants should handle these delivery scenarios This is not a cosmetic enhancement or a nice-to-have feature. This directly impacts: • Order fulfillment success rate • Delivery operations • Customer experience • Merchant adoption of HighLevel Stores • Agency confidence when recommending HighLevel for eCommerce As an agency owner, I have already delivered a live eCommerce project for a paying client and am now facing pushback because delivery teams cannot access customer phone numbers from packing slips. Request: Please add a simple option to display the customer's phone number on packing slips. Even a basic toggle such as: ☑ Show Customer Phone Number on Packing Slip would completely solve this issue. This should be treated as a high-priority eCommerce requirement rather than a feature enhancement, as it affects the core order fulfillment process for merchants.
1
Load More