KKSN Suite
INT — Pro & Enterprise plans

Your ERP, on speaking terms with everything.

Carriers, payments, EDI and files — wired in, logged, and retryable.

Integrations is where the platform meets the rest of your stack: rate-shop the parcel carriers from the order screen, take storefront payments through the gateways you configure, trade EDI documents with your retail customers, and automate file exchange over managed SFTP. Every message in or out is logged with its payload — when something fails, you see it, fix it and retry it from the screen.

  • Multi-carrier rate shopping, label purchase and tracking
  • EDI trading partners with per-partner field mapping — 850, 855, 856, 810 and more
  • Payment gateways with sandbox testing and a full transaction log
  • Managed SFTP partners for automated file drops and pickups
  • A documented REST API — the same one every screen in the platform runs on
erp.acme.ksnsuite.com — Integration activity
✓ carrier rates fetched — 3 quotes, best $12.40
✓ label purchased — tracking 1Z…884
✓ EDI 856 ASN sent — partner NRTH-RETAIL
✓ payment captured — order WS-10382
✓ SFTP drop parsed — 1,240 rows validated
→ EDI 850 received — draft order created
Capabilities

What's included

One admin hub for everything external — shipping, payments, EDI, SFTP and bulk data — with credentials encrypted at rest and every exchange audited.

Shipping gateways

  • Multi-carrier rate shopping. Quote every connected carrier in one call and pick the cheapest service that makes the date — instead of defaulting to the account you've always used.
  • Label purchase and tracking. Buy the rate, get the label and tracking number back, and log it against the shipment — no swivel-chairing into a carrier portal.
  • Per-carrier service control. Enable exactly the service levels you actually use per carrier, so nobody accidentally books overnight air for bin labels.
  • Sandbox before production. Test every carrier connection against sandbox credentials before a single real label is charged to your account.
  • Credentials encrypted at rest. Carrier keys are stored encrypted and served masked — an admin can manage the config without ever reading the secret.

EDI trading partners

For distributors whose biggest customers mandate EDI — onboarding by mapping, not by custom code. Available as an add-on.

  • Trading partner management. Partners link straight to your customer and vendor masters, so an inbound document always knows whose order it is.
  • The standard document set. Inbound 850 purchase orders and 820 payment orders; outbound 855 acknowledgments, 856 ASNs, 810 invoices and 846 inventory status — the set retail programs actually require.
  • Per-partner field mapping. Direct, default, transform, concatenate and lookup mappings per partner per document — each partner's quirks live in configuration, not in code you pay to change.
  • Transaction log with payloads. Every send and receive is stored with its request and response, so a chargeback dispute is answered with evidence instead of a shrug.
  • One-click retry. A failed document is retried from the log after you fix the cause — no re-keying, no asking the partner to resend.
  • Sandbox with sample documents. Prove the mapping against sample 850s and 856s before the first live document ever moves.

Payment gateways

  • Multiple gateway configurations. Configure more than one payment gateway with separate sandbox and production environments — switch or add providers without a migration project.
  • Test connection before go-live. Verify credentials against the gateway's sandbox from the admin screen, so checkout doesn't become the test environment.
  • Storefront checkout, wired here. The gateways you configure are what the WebStore charges against — one place to govern how your money moves.
  • Payment transaction log. Amounts, methods and statuses for every transaction in one grid, so finance reconciles from the system instead of a gateway portal export.
  • Currency and method control. Declare supported currencies and payment methods per gateway, so the checkout only offers what the account can actually settle.

SFTP & file automation

  • Managed SFTP partners. Give each trading partner its own SFTP account with its own folder tree — file exchange stops depending on shared inboxes.
  • Password and key management. Rotate passwords and manage public keys per partner from the admin screen, without a server administrator in the loop.
  • Automated drops and pickups. Files land in partner folders and flow into the platform's import machinery — the overnight feed runs without a human moving files.
  • Backup policies and archives. Exchanged files are archived on the policy you set, so 'what exactly did they send us in March' has an answer.
  • Job history. Every automated run is recorded with its outcome, so a missed feed is a visible failure, never a silent one.

Data in & out

  • Four-step import wizard. Upload, map, validate, commit — bring products, vendors and customers over from your old system without a consultant writing scripts.
  • Auto-mapping and saved profiles. Columns match themselves against a built-in alias table, and the mapping saves as a profile so the second file takes seconds.
  • Row-level validation first. Every row is checked — required fields, types, reference lookups, duplicates — before anything commits, with a downloadable error report naming each failure.
  • Create, update or upsert modes. The same wizard onboards a clean system, refreshes an existing one, or does both at once — you choose what a matching row means.
  • Scheduled BI extracts. Feed your analytics stack with exports in CSV, JSON, Parquet or Excel, with previews and a run history per feed.
  • A real REST API underneath. Everything the screens do is a documented, tenant-scoped REST endpoint — anything we can do, your developers can too.
EDI

The retail program says EDI or no PO. Say yes by Friday.

Winning a big retail account usually means a compliance packet: 850s in, 855s, 856s and 810s out, each with the partner's own field conventions. Here that's a trading partner record and a mapping screen — direct mappings for the easy fields, transforms and lookups for the awkward ones — proven against sample documents in the sandbox before anything live moves.

  • Mapping, not programmingeach partner's format quirks are configuration you can read and change yourself.
  • Evidence for every exchangefull request and response payloads on every transaction, kept and searchable.
  • Failures retry from the logfix the cause, click retry — the document flows without being rebuilt.
EDI — Transaction log
DocPartnerDirectionStatus
856 ASNNRTH-RETAILOUTSENT
850 PONRTH-RETAILINPROCESSED
810 INVVALU-MARTOUTSENT
855 ACKVALU-MARTOUTRETRIED · SENT
Data migration

Twenty years of catalog in by lunch. Validated first.

The import wizard is how tenants leave their old system without leaving their data. Upload the spreadsheet, let the columns map themselves, then watch validation grade every row before a single one commits — bad references, missing fields and duplicates come back as a named, downloadable list instead of a corrupted master file you discover in month three.

  • Nothing commits unvalidatedthe wizard refuses bad rows up front — your product master starts clean and stays clean.
  • Error reports you can hand backrow-by-row failures with reasons, ready for whoever owns the source file.
  • Profiles make it repeatablesave the mapping once and the monthly vendor file becomes a two-click routine.
Data Center — Import jobs
JobEntityStatus
IMP-0187PRODUCTVALIDATED
IMP-0186CUSTOMERCOMMITTED
IMP-0185VENDORCOMMITTED
IMP-0184PRODUCTCOMMITTED
MappingValidationCommit
Questions

What buyers ask

Which shipping carriers can we connect?

The shipping gateway connects the major parcel carriers through one integration, with your own carrier accounts and negotiated rates. You enable each carrier and each service level individually, test it in sandbox, and rate-shop across all of them from the order screen.

Our biggest customer mandates EDI. How painful is onboarding?

Create the trading partner, map their fields per document type, and prove the mapping against sample documents in the sandbox. The awkward partner-specific conventions are handled by transform and lookup mappings in configuration — there is no per-partner custom code to commission or maintain.

What happens when an EDI document fails?

It lands in the transaction log with its full request and response payloads and a status you can filter for. Fix the cause — a mapping, a missing reference — and retry it from the log. Nothing silently disappears, and nothing needs to be re-keyed.

Can we migrate our data in ourselves, without consultants?

That's what the import wizard is for: upload products, vendors or customers from a spreadsheet, review the auto-mapped columns, and validate every row before committing. Failures come back as a downloadable, row-by-row error report — you fix the file, not the database.

Is there an API for our own developers?

Yes — and it isn't a side door. Every screen in the platform runs on the same documented REST API, with tenant-scoped authentication and consistent list, filter and pagination conventions. If the product can do it, your integration can call it.

What's included in which plan?

Shipping gateways, payment gateways, SFTP automation, the import wizard and the API ship with the Pro plan and up. EDI trading-partner integration is an add-on from $25 per user per month. During the 14-day trial, all of it is on.

Connect the stack. Keep the receipts.

Fourteen days with every gateway, the EDI sandbox and the import wizard switched on — bring a carrier account and your ugliest spreadsheet and see both handled before the trial ends.

14 days · every module · no card