What these systems normally control
Requirements for assessment; confirm supported actions before relying on this workflow.
Content, checkout, catalog, storefront personalization, and — in some setups — customer accounts.
Website and E-Commerce
Connect website requests and orders to the work that follows.
Provider options and connection limits
Providers to assess for website and e-commerce
WordPressNeeds assessment
ShopifyNeeds assessment
SquarespaceNeeds assessment
WixNeeds assessment
Check the actual connection before changing your process.
On Pro, the QuickBooks Online connection imports customers and invoices from your own company and does not write back. It still needs checking with your company. Other provider names and the information flows below describe requirements to assess, not ready-to-use connections. Confirm the provider, plan, permissions, direction and any setup cost before work begins.
Why the specialized system usually stays
Requirements for assessment; confirm supported actions before relying on this workflow.
The website is the front door. Content management, SEO, and design belong in a CMS. E-commerce checkout belongs in a store platform. The Forge connects so leads, purchases, and customer status flow into your connected business record.
Information to review for import
Requirements for assessment; confirm supported actions before relying on this workflow.
- Form submissions from the website
- Orders, order status, and refunds
- Customer account creation and updates
- Product catalog references
Information to review for export
Requirements for assessment; confirm supported actions before relying on this workflow.
- Order-related communication
- Customer status changes back to the storefront (loyalty, VIP)
- Suppression / audience membership updates
Events to consider during setup
Requirements for assessment; confirm supported actions before relying on this workflow.
- Order placed
- Order refunded
- Customer account created
- Cart abandoned (where the provider emits it)
Manual work the proposed connection may reduce
Requirements for assessment; confirm supported actions before relying on this workflow.
- Copying orders into your business record by hand
- Attributing storefront customers to the right sales rep manually
- Maintaining a separate follow-up list for online buyers
Whose work improves
Requirements for assessment; confirm supported actions before relying on this workflow.
- Sales and marketing leader
- Office administrator
- Finance and accounting
- Owner / executive
Reports that become possible
Requirements for assessment; confirm supported actions before relying on this workflow.
- Revenue by product, campaign, and customer
- Repeat-purchase behaviour
- Time from order to fulfillment
Access and permission notes
Requirements for assessment; confirm supported actions before relying on this workflow.
- PCI scope stays with the storefront's checkout.
- Only tokenized customer identifiers are stored in The Forge.
Common category-wide limitations
Requirements for assessment; confirm supported actions before relying on this workflow.
- Complex storefront customizations may need custom mapping.
- Real-time depends on the storefront's webhook reliability.
What might be replaced after review
Requirements for assessment; confirm supported actions before relying on this workflow.
The Forge does not replace a CMS or a storefront. It replaces the manual copy work between them and your connected business record.