# Complex B2B in 7 Days - Funded POC for Qualified Clients - Content Cucumber > A funded Shopware POC for qualified midmarket B2B. Customer-group pricing, ERP integration, punch-out, multi-org, and approval routing demoed on a working URL on your real data. *Source: [https://contentcucumber.com/midmarket-b2b-poc/](https://contentcucumber.com/midmarket-b2b-poc/)* --- ## Complex B2B in 7 days (For qualified midmarket B2B. Funded POC.) Midmarket B2B is complex. Quote-based and contract pricing per customer group, with volume breaks and negotiated tiers. Multi-org logins, multi-warehouse inventory, multi-currency in one install. Punch-out catalogs, approval routing, and spend limits per buyer. Tax exemption flows, resale certificates, net terms, and PO numbers. Dealer portals layered over a public catalog. ERP-driven data running through all of it. A lot of moving parts. Lighter platforms ask you to fit your business into their model. The right platform plugs into yours. For qualified midmarket B2B, a proof of concept on Shopware closes that question first. Your real catalog, your real workflows, on a working URL ready to click through, demo internally, and hand to procurement. We already built one ourselves. Real cart, real checkout, B2B in the box. Use the form to start a fit conversation, or click through the live demo first. ## What lighter platforms cannot absorb The operational reality of manufacturing, distribution, regulated commerce, and heavy industry. Four moving parts that break standard ecommerce. #### Customer-group pricing tied to your ERP Contract prices, negotiated tiers, branch-specific discounts, dealer pricing, tax exemption certificates. The numbers live in your ERP, not a second copy on the storefront. Most platforms force the duplication and lose the audit trail. #### Multi-org, multi-warehouse, multi-currency One buying group, many subsidiaries, regional warehouses, multiple currencies, order-splitting across branches. The platform handles it natively or it does not. There is no middle option once you are at scale. #### Punch-out, OCI, SAP Ariba Procurement teams expect catalog feeds in the format their system wants. If the platform cannot speak the procurement language your buyers use, the deal stalls at the IT review. This is a baseline requirement. #### Approval chains and audit trail Buyer rep submits, manager approves, finance signs off. Spend limits per buyer, custom approval rules per category, full audit trail for compliance. Bolt-on plug-ins do not survive the second acquisition. ## This decision is *operational.* (The replatform decision) Traditional B2B platform decisions run twelve weeks of discovery and end in a six-figure SOW, slides, a Figma file, and a wireframe deck. What you do not get is anything that touches your ERP, your customer-group pricing, or the dealer portal you have been patching together for years. The operational question stays open until day one of the build. A POC closes that question first. We took Shopware and built Cucumber and Co., a fictional 200-year-old B2B distributor, in seven days. Customer-group pricing, real cart, real checkout, B2B-ready out of the box. Click through and place a test order. [Open the live demo →](https://shopware.contentcucumber.com) [](https://shopware.contentcucumber.com)Cucumber and Co. on Shopware. Real cart. Real checkout. Try it. ## Shopware for serious B2B (Our recommended platform) Shopware ships B2B in the same install as B2C. Customer-group pricing, multi-storefront, multi-region, multi-currency, an advanced rule-builder that routes business processes without custom development, and a self-hosted option that matters when regulated data is in scope. It meets the business where it is. Content Cucumber is an official Shopware partner. [Read our Shopware partner profile →](https://contentcucumber.com/partners/shopware/) ## What a qualified POC typically delivers Scope is finalized on the discovery call. When a POC runs, this is the shape it takes. By day seven, these are on a working URL ready for internal review. #### Catalog with your data shape Ten to fifty representative SKUs imported with your real metadata, certifications, MOQs, customer-group pricing, and ERP keys preserved. Real merchandising on your shape. #### Quote workflow demoed Quote request from the buyer side, review and approval from the admin side. Real numbers, your contract terms, your approval chain. #### Punch-out feed proof An OCI feed pointed at a test procurement system. Optional SAP Ariba CIF setup if your buyers require it. IT-reviewable on day seven. #### Approval routing live Buyer rep, manager approve, finance sign-off chain configured against your spend limits. Full audit trail captured. #### Multi-org and dealer portal demo One buying group, many subsidiaries, separate price books per org, gated dealer experience over a public catalog. Same backend, different storefront per audience. ## The seven-day arc ## The seven-day arc The same pattern we run for every qualified POC, scoped to the moving parts your team flagged on the discovery call. #### Stack and scope Stand up Shopware in Docker. Map your moving parts to platform primitives: customer groups, contract pricing, approval rules, ERP integration shape. No surprises after this day. #### Catalog import Bring in ten to fifty representative SKUs with B2B metadata (MOQs, customer-group pricing, certifications). Content Cucumber writes descriptions and category copy if you hand us a catalog CSV. #### Customer groups and pricing Configure customer-group pricing, contract prices, and volume breaks against your real numbers. Tiered storefront experience per buying group. #### Quote and approval Quote request workflow live on the storefront. Approval routing configured against the spend limits and approval chain you describe on day one. #### Punch-out integration OCI feed wired up against a test procurement system. Optional SAP Ariba CIF setup if your buyers require it. #### Cart, checkout, orders Real cart, real checkout, real order numbers on your data shape. Net terms, PO numbers, tax exemption flow, and cost centers as applicable. #### Walkthrough and decision Working URL ready for your team to demo internally. Walkthrough call. Discovery findings and a production scope proposal. Your call from there: sign a production cutover contract, refine the scope, or walk away clean. ## Frequently asked questions ### What qualifies a client for the POC? [NEED ANSWER FROM BRENT: what 'qualified' means in practice, how the Shopware funding mechanic works, what's in and out of scope] ### Can the POC run against our real ERP and procurement systems, or only sample data? [NEED ANSWER FROM BRENT: how integration scope is handled in the POC, what is in-scope vs follow-up SOW] ### How does the POC handle punch-out from SAP Ariba or Oracle Procurement? [NEED ANSWER FROM BRENT: which punch-out flavors are demoed by default vs add-on] ### Will the POC demo our actual customer-group pricing, or generic tiers? [NEED ANSWER FROM BRENT: how customer pricing is loaded from client data] ### What happens on day eight if we move forward? [NEED ANSWER FROM BRENT: the three-path outcome (sign the production cutover contract to build the real site, keep refining scope on the POC, or walk away). Code and production work require a signed paid contract. The POC is a sales demo, not a build deliverable.] ### Can the POC be hosted on our AWS, Azure, or GCP account? [NEED ANSWER FROM BRENT: hosting model, who pays for cloud, what gets handed off] ## Start the fit conversation Manufacturing, distribution, HVAC, regulated commerce, heavy equipment, aerospace, MRO. Tell us about your catalog, your ERP, your procurement integrations, and the parts of your business your current platform fights you on. If we fit and you qualify, the POC runs from there.