Items, price levels, inventory by location and sales orders, through documented endpoints that survive a NetSuite release.
Ready-made connections, scoped before we quote a timeline. Integrations are the real driver of a replatform schedule.
The specific answer, because a page that says "seamless integration" tells an evaluator nothing they can act on.
Object | Direction | Sync | Notes |
|---|---|---|---|
Item records | Read | On change | Part identity, base attributes and item-level configuration. |
Price levels | Read | On request | Customer-specific price levels and volume breaks resolved per account. |
Inventory by location | Read | Near-real-time | Multi-location availability, including branch stock where you run one. |
Sales orders | Write | On submit | Orders created with line items, customer part numbers and shipping preference. |
Customers and contacts | Read | On authentication | Account resolution and contract terms. |
Saved searches | Read | Scheduled | Where your operational logic already lives in a saved search, we consume it rather than reimplement it. |
Field-level mapping is agreed during scoping. Customisation in your instance changes the mapping, not the model.
We connect through NetSuite's standard web services (SuiteTalk REST). Custom NetSuite scripts that already hold your business rules are reused, not rebuilt.
Multi-subsidiary configurations are supported and need to be scoped early. Which subsidiary an order belongs to affects pricing, tax and availability together.
Present, Partial or Missing, each rating followed by the specific observation behind it. Five business days, and there is no call first.