Celeste library
For ERP partners and VARs
Written for the person who spots the commerce need first. How to qualify a commerce opportunity attached to an ERP deal, what to scope yourself, what to hand off, and how to tell a client the honest answer without losing the deal.
How to qualify a commerce opportunity inside an ERP deal
Ask three things early: does price depend on who is buying, does availability depend on which warehouse serves them, and has any customer already asked for punchout or EDI. If all three answers are no, the commerce project is a native Acumatica or Cin7 connector build that most VARs can deliver themselves. Each yes moves the work toward custom pricing logic, middleware and a specialist.What "Fulfilled by Acumatica" actually means
Fulfilled by Acumatica means Acumatica bills for the application and holds the vendor to an update cadence. Acumatica’s own blog describes it as a hand-selected tier requiring 10 or more satisfied mutual customers and a commitment to the Always Current programme, sold on Acumatica’s price list. It sits on top of the technical certification that every Marketplace listing already carries, and it is not a statement that the app fits your client.Certified, validated, or just Marketplace listed
Three different things get called certification. Acumatica Certified Application is a technical review by an Acumatica test engineer and is a condition of listing at all. Fulfilled by Acumatica is a commercial tier on top of it. A vendor calling itself "validated" or "integrates with" usually means neither. None of the three guarantees the vendor’s pricing model survives contact with your client’s price book.What attaching commerce does to an ERP deal, in both directions
Attaching commerce to an Acumatica or Cin7 deal raises contract value, adds a retention hook that makes the ERP expensive to displace, and gives the client a visible win their customers can see. It also adds a second go-live, a second vendor, and a hard dependency on item data quality that the ERP project alone would never have tested. Sequencing decides which of those two you get.Keep it, subcontract it, or refer it
Keep the commerce work when it is a native connector, a themed storefront and a catalogue exercise, which describes most commerce projects attached to an Acumatica or Cin7 deal. Subcontract when you want the margin and can carry the warranty. Refer when a delivery failure would land on your ERP renewal. Relationship exposure, not margin, is the column that usually decides it.Who owns the integration defect?
Orders stop posting at four o’clock on a Friday. The VAR says Acumatica is fine, the agency says the platform returned a rate limit error, and the platform tells the client to contact the app developer. Assign ownership by symptom rather than by system, name one triage owner who is paid to look first, and put both in the statement of work before go-live rather than during the outage.When the storefront underperforms, the ERP renewal takes the blame
Clients attribute by proximity rather than by cause. A storefront that converts badly, shows a list price to a contract customer, or takes a day to reflect stock gets described in the renewal meeting as a problem "since we went on Acumatica". Instrument attribution before launch: a pre-launch baseline, a defect ledger that separates integration faults from merchandising, and one monthly number the client has agreed means success.How do you estimate a commerce attach before you have seen the item master?
You cannot honestly estimate catalogue and pricing work without data, so quote those two as a paid discovery and fix-price the rest. Ask for six exports: stock items, customers with price class and currency, the sales price worksheet or customer-item price list, 12 months of order lines, the item cross-reference table, and the warehouse list. Each one answers a question that moves the estimate more than any feature list will.Where commerce fits for a Cin7 partner
Cin7 Core ships a B2B customer portal that is genuinely enough for a wholesaler selling from price tiers with a modest catalogue and no marketing ambitions, and a Cin7 partner should say so rather than sell past it. It runs out at pricing depth, product content and search, multi-brand, and anything the client wants to control themselves. On Cin7 Omni, Legacy B2B reaches end of life on 23 November 2026, which is a dated conversation a partner should be starting now.Twelve commerce questions to add to your ERP discovery script
Twelve questions, one for each requirement that decides whether the native Acumatica or Cin7 connector is enough. Each comes with what a good answer sounds like, what a bad answer sounds like, and what the bad answer costs. Ask them inside a normal ERP discovery and you will know the shape of the commerce project before anyone has named a platform.