Website Builder Store Connector

The problem

A brand that started on a hosted website builder usually runs its first few years on exports. Someone downloads a CSV of orders each morning, cleans it in a spreadsheet, and keys the results into an ERP or an accounting package. When that brand moves onto NetSuite, the spreadsheet does not go away — it gets worse, because now there is a real subsidiary structure, real item records, real revenue recognition and real inventory commitments waiting on data that arrives once a day, by hand.

The larger e-commerce platforms have integration options. Hosted website builders sit in an awkward gap: the store is real, the order volume is real, but the tooling assumes you are either tiny enough to work manually or large enough to fund a bespoke middleware project. The result is a NetSuite account where the sales channel that actually pays the bills is the one part of the business that nobody trusts, because the numbers are always a day behind and always slightly wrong.

The failure modes are predictable. Duplicate customers accumulate because the same shopper checks out under two email casings. Stock sells that was already committed to a wholesale order. Tax on an order is recalculated during re-keying and no longer matches what the shopper was charged. Refunds get handled in the storefront and never reach NetSuite at all.

What ECOSIRE builds

ECOSIRE builds a connector inside your NetSuite account as an SDF project, delivered as an unmanaged bundle you own outright. There is nothing to subscribe to and no data passing through our infrastructure.

Order ingestion

A RESTlet built on SuiteScript 2.1 receives store order payloads, or a Scheduled Script polls your store's order endpoint on an interval you choose — whichever your platform supports. Each order lands in a staging custom record (customrecord_eco_wsb_order_stage) holding the raw payload, a store order identifier, a processing status and an error log field. Nothing writes to a transaction record until the payload passes validation, so a malformed order never leaves a half-created Sales Order behind.

A Map/Reduce script drains the staging queue and creates the Sales Order, applying your configured order form, location, department and class defaults. Store order identifiers are written to a custom body field and checked with a saved search before creation, so replayed webhooks and re-polled pages cannot produce duplicate transactions.

Customer matching

Customers are matched on normalised email first, then on a configurable fallback of name plus billing postcode. Matching runs against a saved search rather than a naive record load, so it respects your existing customer hierarchy. New customers are created under the subsidiary you nominate, with the store as the lead source and the store customer identifier on a custom field for future lookups. In OneWorld accounts, the target subsidiary is resolved per store, so a two-store brand does not collapse into one legal entity.

Items, pricing and inventory

Store SKUs map to Inventory Items, Non-Inventory Items or Kit/Package Items through a mapping custom record. Unmapped SKUs do not silently create junk item records — the order is held in staging and flagged for review. A Scheduled Script pushes available quantity back to the store using the item's Available or Available to Promise figure from an Inventory Item saved search, netting out the locations you exclude. Price levels can be pushed from a nominated price level so a promotional change in NetSuite reaches the storefront without a second edit.

Payments, refunds and fulfilment

Captured store payments create a Customer Deposit or a Customer Payment against the Sales Order, posting to the undeposited-funds or bank account you configure per payment method. Store refunds create a Credit Memo, or a Customer Refund where the money has genuinely left. When an Item Fulfilment is created in NetSuite, a User Event script sends tracking numbers and carrier back to the store so the shopper's order status updates without anyone logging into two systems.

Tax, shipping and discounts

The amounts the shopper actually paid are what we post. Store-calculated tax is written to a tax line or a designated tax code rather than being recalculated by NetSuite, so the Sales Order total reconciles to the payment gateway to the cent. Shipping arrives as a shipping cost or as a nominated Other Charge item; discounts arrive as a Discount Item line or a header-level discount, whichever matches your revenue reporting.

Errors you can see

Every sync attempt writes to a log custom record with the payload, the outcome and the NetSuite internal ID it produced. A saved search and a dashboard portlet show failed orders in one list. A SuiteFlow workflow escalates anything stuck beyond a threshold you set, emailing the owner instead of leaving a silent gap in the day's revenue.

Who this is for

Brands doing enough volume that manual entry has become a genuine cost, but running on a hosted website builder rather than a dedicated e-commerce platform. Typically one or two storefronts, a single subsidiary or a small OneWorld structure, and a finance team that wants the sales channel to close cleanly at month end. It suits companies that would rather own the code than rent a connector.

How delivery works

Scoping call. We walk through your storefront's available API or export mechanism, your NetSuite edition and subsidiary structure, the item types in play, your tax treatment and how you want payments to post. We look at your actual order payload, not a generic sample.

Fixed quote. You receive a written scope covering the record mappings, the scripts to be built and the acceptance tests. The price is fixed for that scope. If you later want more, that is a separate quoted change.

Build. ECOSIRE develops the connector against your requirements as an SDF project under version control. Typical lead time is two to four weeks from a signed scope, depending on how many item types and payment methods are in play.

Install in sandbox. We deploy to your sandbox or a Release Preview account first, load a representative set of your real orders, and walk through the results with you — order totals, tax, customer matching, inventory movement.

Install in production. After sign-off we deploy the same bundle to production, configure the setup record, enable the deployments and monitor the first days of live traffic with you.

Support. A support window is included from go-live for defect fixes against the agreed scope. Extended support and enhancement work are quoted separately.

What you should know before you buy

This is a build-to-order engagement, not a download. Nothing ships until it has been scoped and built for your account. What is possible depends on what your website builder exposes: some platforms provide webhooks and a full order API, others only a polled export. We establish that on the scoping call before you commit to anything, and if your platform cannot support the sync you need, we will tell you rather than quote around it.