Help Articles
Every franchise website needs brand templates, a page for each location with a store locator, forms and analytics that work by location, and fast, mobile-friendly, accessible pages. Depending on how your network runs, it may also need franchise recruitment pages, franchisee access with approvals, an online store with stock and orders by location, a portal where store teams manage online orders, and a B2B portal for trade and business customers.
It depends on the setup, the number of locations and the integrations the website needs. Location page tools and franchise website builders often charge per location per month. Platforms and custom builds usually charge a license or subscription plus a one-off build. Ask each vendor what the website costs at your current number of locations and at double that number, what it costs to add one location, and what ongoing maintenance includes.
Yes, if the platform supports permissions by location. Head office keeps the brand, templates, products and prices, and opens only the fields each franchisee needs, such as opening hours, local offers, events and photos. Franchisee changes go to head office for approval before they go live, and every change is recorded with who made it and when.
Give franchisees their own websites when they run as independent businesses, sell different products or services, or joined the network with websites of their own. Otherwise, a page or microsite for each location on your main website is simpler to run: one brand, one domain building search presence, and one set of templates to maintain. If franchisees do need their own websites, build them from one brand template on one platform, so head office can still update the brand and shared content across every site.
Franchise website development is building the website setup a franchise network runs on. That covers the brand template, a page, microsite or website for each location, the access each franchisee has, and the integrations with stock, orders, bookings and point of sale. Common setups range from one central website with a page for each store to separate franchisee websites built from one brand template.
Most franchise networks go live in 6 to 10 weeks, and the people who build the platform run the implementation.
- Week 1: we map your locations, catalog, store data and who edits what.
- Weeks 2 to 5: your templates, the location page template, head office and franchisee permissions, and the catalog and stock feeds.
- Weeks 6 and 7: content is migrated and mapped, redirects are set up, and each location's team is onboarded.
- Weeks 8 to 10: launch, with your implementation lead on standby.
After launch the same team stays on, with a dedicated success manager and quarterly business reviews.
Yes. Many partners start by referring and move to Build once their team is trained.
No. Training and a private sandbox come after approval, at no cost.
Build partners start at Gold. After 12 months, your level follows how involved you are in sales, build and support.
We review every application within 2 business days. Your partner manager then contacts you to confirm your path and book your orientation.
Where prices, credit limits, stock, order history and invoices live, and whether each can be read in real time or only in batches. Check the quality of customer and product data, and list the ERP processes the website must trigger, such as creating customers and sales orders.
Most platforms connect to EDI through an EDI provider or a partner app. As of October 2026, none of Adobe Commerce, BigCommerce B2B Edition, Shopify, Salesforce B2B Commerce, OroCommerce, Sana Commerce or Optimizely Configured Commerce documents built-in EDI. What matters is whether EDI orders land in the same order record, customer account and reports as online orders. On Core dna, EDI runs through the supplier's existing EDI software, connected in the Orchestration module.
EDI sends business documents (purchase orders, acknowledgments, shipping notices, invoices) directly between the buyer's and the supplier's systems, with no website involved. Punchout lets a buyer open the supplier's website from their procurement system, such as SAP Ariba, Coupa or Jaggaer, build a cart at contract prices and send it back for approval. The approved purchase order then reaches the supplier, sometimes by EDI.
Customer-specific pricing from the ERP, account terms and credit limits, quotes and approvals, and a buyer portal with order and invoice history. Suppliers selling to large accounts also need EDI and punchout. Product data, search built for part numbers, and reliable ERP integration decide whether buyers use the site.
Yes. The Core dna MCP server connects AI assistants such as Claude and ChatGPT to the platform. The agent works with the same role as the person using it and cannot skip approval steps.
Every change an agent makes is saved as a revision, so your client can review it and roll it back.