Integration combo
SFTP Connector to NetSuite integration
Not every system in a retail estate has a modern API. Legacy ERPs, in-house tools and long-running vendor systems still talk in files: a daily orders.csv on an SFTP server, a stock.txt drop at midnight, a fixed-width customer extract on the hour. We pick those files up, parse them, validate them, and synchronise the contents into NetSuite as proper records, with the same monitoring and SLA we apply to API-first integrations. Built and supported as a certified Patchworks Partner Agency.
Flow shape
File ingest: SFTP to NetSuite
How a .csv or .txt file landing on an SFTP server becomes a set of NetSuite records with parsing, validation and error handling in place from the first drop.
- Trigger SFTP File arrives scheduled poll or watcher
- Extract Patchworks Fetch + checksum atomic move to working folder
- Transform Patchworks Parse rows CSV / TXT / fixed-width schema
- Decision Patchworks Schema valid? row-level reject to dead letter
- Transform Patchworks Map to NetSuite record type, subsidiary, dimensions
- Action NetSuite Create / update via SuiteTalk / RESTlet, batched
- Writeback SFTP Archive + receipt move to /processed, write log
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
5 synchronisations between SFTP Connector and NetSuite.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
SFTP Connector NetSuite
Orders raised in SFTP Connector flow into NetSuite on creation, status change and edit. The flow normalises SFTP Connector's order schema into the record shape NetSuite expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so NetSuite stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Inventory sync
SFTP Connector NetSuite
Stock levels in SFTP Connector push to NetSuite on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where NetSuite has its own location model we map SFTP Connector's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with SFTP Connector retaining authority.
- 03
Product sync
SFTP Connector NetSuite
Product master data syncs from SFTP Connector to NetSuite on publish, with channel-aware enrichment so NetSuite only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where NetSuite has channel-specific requirements that SFTP Connector does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 04
Pricing sync
SFTP Connector NetSuite
Price lists in SFTP Connector push to NetSuite with currency, tax-class and customer-group awareness intact. Promotional pricing, contract pricing and tiered B2B pricing are handled as first-class concepts rather than overrides applied at the storefront. Where SFTP Connector runs effective-dated pricing, the flow coordinates the cutover so NetSuite's catalogue switches at the same instant as the finance side rather than drifting by hours. Currency rounding and display-tax rules are reconciled at the integration boundary to avoid the classic 1p / 1c off-by-one that haunts multi-currency rollouts.
- 05
Customer sync
SFTP Connector NetSuite
Customers created or updated in SFTP Connector flow into NetSuite with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to NetSuite's defaults. Where NetSuite is the customer system of record (CRM or ERP) we publish back into SFTP Connector so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
Typical delivery
3 to 6 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: file formats, drop cadence, NetSuite record-type mapping, error-handling policy.
- Weeks 2 to 3 Build: pickup, parse, validate, map, post and archive flows in Patchworks.
- Weeks 4 to 5 Integration testing using real legacy file samples against the NetSuite sandbox.
- Week 6 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes SFTP Connector to NetSuite.
Patchworks handles file-based sources as a first-class flow shape rather than a fallback. We build the SFTP-to-NetSuite integration in Patchworks with explicit file pickup, parsing, schema validation and dead-letter handling for malformed rows. The merchant sees the same monitoring, retry behaviour and on-call cover for a CSV drop as for a webhook from Shopify. Where the legacy system can also accept files back, the same Patchworks integration can publish outbound extracts on schedule.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 What file formats do you support?
CSV, TSV, fixed-width text, pipe-delimited and most variants in between. Where the source produces an unusual flavour (mixed delimiters, embedded headers, multi-record per line), we build a custom parser at the integration boundary. XML and JSON dropped on SFTP are also handled. -
02 How are malformed rows handled?
Bad rows route to a dead-letter folder with the original line and a parse-error reason logged. Valid rows in the same file still process. Finance or operations can review the dead-letter file, fix the source data, and re-drop. Nothing silently corrupts the NetSuite side. -
03 What about character encoding, line endings and BOMs?
Handled explicitly. UTF-8 with or without BOM, Windows-1252, ISO-8859-1, mixed CRLF / LF line endings. We agree the encoding at scoping rather than guessing, and the parser fails loudly if a file arrives in an unexpected encoding rather than corrupting the data on the way in. -
04 Can the integration push files back to the legacy system?
Yes. The same Patchworks integration can publish outbound extracts from NetSuite to SFTP on schedule: stock counts, posted invoices, settlement reports, anything the legacy system needs to consume. Filename, folder, and format conventions match whatever the legacy system expects. -
05 Do you support SFTP-to-NetSuite under SLA after go-live?
Yes. The same team that builds the integration runs it under retainer. File-pickup monitoring, on-call cover, monthly health checks and tiered response SLAs from £750/month. Missed file drops alert before the next batch posts late.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.