> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/connected-apps/shopify/installation-guide/configuration-settings/b2b-sync/business-cases-and-faqs.md). # Business Cases and FAQs ### **Business Cases (Real Use Cases)** *** #### **Business Case 1 — Same Client, Multiple Locations, Different Pricing** #### Problem A client has multiple stores but wants different pricing per store. #### Solution * Use **location-based pricing (customer + location mapping)** *** #### **Business Case 2 — Orders Not Getting Created** #### Problem Orders fail during sync. #### Root Cause * No default customer * Missing custom field setting #### Solution * Create default customer * Enable required settings *** *** #### **Business Case 3 — Pricing Not Applied** #### Problem Orders are created but pricing is incorrect. #### Root Cause * Item mapping missing * Custom field not configured #### Solution * Map item ID * Enable B2B price sync *** #### **Business Case 4 — Same Pricing for Entire Company** #### Problem Company wants one pricing across all locations. #### Solution * Use **customer group-based pricing** *** ### **FAQs** *** ### **Q1. Why are orders created under customers and not companies?** Because orders are always linked to **customers (locations)**.\ Companies act as parent entities for grouping. *** ### **Q2. Why is the default customer required?** To ensure orders are created even when mapping is missing. *** ### **Q3. Why is pricing not syncing?** Possible reasons: * Item not mapped * Custom field missing * Required settings not enabled *** ### **Q4. Can pricing differ for each location?** Yes, using **location-based pricing rules**. *** ### **Q5. Why is currency important?** Order creation requires matching currency between: * Customer * Account *** ### **Q6. What happens if the item does not exist in the ERP?** Pricing rules will fail.\ The Item must be mapped using custom fields. *** ### **Q7. What is the difference between the two pricing methods?** * **Customer Group Pricing** → Same price for company * **Customer/Location Pricing** → Different prices per location *** ### **Final Understanding** *** #### **What B2B Sync Does** * Creates structured company hierarchy * Enables location-based order handling * Applies flexible pricing rules *** #### **Core Concept** 👉 **Company = Structure**\ 👉 **Customer (Location) = Transaction unit**\ 👉 **Pricing = Controlled by mapping & rules** *** #### **One-Line Summary** **B2B Sync ensures that companies, locations, and pricing are connected correctly so that orders are created accurately and pricing is always applied as intended.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xorosoft.com/xoroerp-1/connected-apps/shopify/installation-guide/configuration-settings/b2b-sync/business-cases-and-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.