Move the agreed configuration, pricing and quoting scope into Threekit. Map any unsupported requirements before implementation begins.
Use Threekit for requirements and configuration, then hand the result to the existing system. Define the integration and rule-maintenance responsibilities up front.
Before choosing a deployment, check these requirements against the functions your team uses today.
Volume pricing, rebates, entitlements, contracts and subscription pricing are outside the stated Threekit scope.
Manufacturing BOM and CAD output are outside scope.
Threekit sends a JSON or XML payload. Your team or integrator scopes the receiving workflow.
The implementation uses a blueprint, not a packaged connector.
Your team owns updates; an alongside deployment needs a plan for keeping duplicated rules aligned.
