Starts in NetSuite. Ends in NetSuite.

A company connects NetSuite once. After that, NesoTMS shows the orders that are packed and ready to ship on its Clerk Station. Someone opens one, checks the boxes, picks a carrier service from the rate comparison, and clicks Buy & print. NesoTMS buys the label directly from the carrier, prints it (in the browser or on a shipping station), and then updates the same item fulfillment in NetSuite.

NetSuite stays your system of record for orders, customers, items and inventory. The carrier work happens in NesoTMS: rating, buying, voiding and keeping the label files. In the standard setup NetSuite supplies the orders and receives the write-back.

NesoTMS uses NetSuite's token-based authentication. In NetSuite you create an integration record with token-based authentication turned on, and an access token for the user and role that will run NesoTMS. NesoTMS asks for your account ID, the RESTlet URL of the NesoTMS connector in your account, and four values: the consumer key and secret from the integration record, and the token ID and secret from the access token.

NesoTMS reaches your account only through the connector, signed with those four values. They are encrypted with AES-256-GCM before they are stored and can't be read back: after saving, the setup page shows only the last four characters of the consumer key and token ID. Only a company administrator can save or replace them.

The Test connection button sends a read-only request and reports the NetSuite account and environment, the user and role the token runs as, and the connector's version. When NetSuite refuses, NesoTMS shows NetSuite's error with a hint, such as a rejected login or a role that isn't allowed to run the connector. Troubleshooting lists the usual causes.

The connector is the part of NesoTMS that lives in your NetSuite account: a few scripts, the records they keep and the NesoTMS Connector role. NesoTMS installs it for you. You turn on six NetSuite features, add a certificate NesoTMS makes for your account in NetSuite, using the Administrator role, and paste the Certificate ID back. NesoTMS then installs the connector and, after a successful install, deletes the certificate's private key. The certificate is valid for seven days, and you can revoke it in NetSuite as soon as the install finishes.

Setup also has an Install the bundle choice, for a NesoTMS bundle in NetSuite's SuiteBundler. It shows as Coming soon until that bundle is published. If the connector is already in the account, the installer stops with a message instead of overwriting it. Before you connect lists what to prepare, and Connect NetSuite has every step.

When someone opens a fulfillment, NesoTMS reads its ship-to address, the ship-from address from the fulfillment's location, the package lines already on it, the item quantities and weights, the current ship method, the customer name and the sales order it came from. When there is no location at all, it falls back to the subsidiary's address and then the company's. A location with an unusable address is never skipped: NesoTMS names what is wrong so it gets fixed in NetSuite instead of shipping from somewhere else.

For shipments from the US to Canada it also reads the sales order number, the PO number, the currency and each item's description, HS code and country of manufacture to prefill the commercial invoice. When the declared value option is on, it works out the order value from the fulfillment's quantities and the sales order's prices.

An item fulfillment moves through three ship statuses: Picked, Packed and Shipped. NesoTMS imports Picked and Packed by default, because those are the ones that still need a label. A purchase sets Shipped. Voiding the last active label sets Packed again. Voiding one label of several leaves the status at Shipped, because another label is still active.

Sometimes NetSuite accepts the new status value but refuses the save, for example when the fulfillment is dated in a closed period or a workflow guards the Shipped status. NesoTMS then saves the packages, tracking numbers and cost without the status and shows a warning that NetSuite refused the status change, so someone can set it by hand. The label is never lost over a status.

Each box becomes one package line with its own tracking number. Identical boxes can be entered as one row with a quantity, and NesoTMS expands them into separate packages. UPS and FedEx labels support up to 10 packages in one purchase. NesoTMS replaces the lines in the package list the fulfillment uses: the UPS, FedEx, USPS or generic Package list.

If your fulfillments already carry package lines with sizes, the ship page starts with those boxes and rates load by themselves. If they don't, a packer enters each box once.

When part of an order ships, NetSuite makes one item fulfillment for that part. NesoTMS treats each fulfillment as its own shipment, with its own boxes, labels and write-back. In sales order mode, an order's page lists every line with the quantity ordered, fulfilled and remaining, and links to the order's fulfillments. A partial fulfillment's declared value is its own share: its quantity times the sales order line's rate.

In sales order mode, packing an order at the Packing Station makes its item fulfillment: one new fulfillment for everything left on the order, in Packed status, with the packed boxes. An order whose lines need inventory detail (bins, lots or serial numbers) is packed in NetSuite instead.

NesoTMS never edits the item lines of a fulfillment, and it doesn't read or change inventory detail (lots, serial numbers or bins). It reads item quantities and weights to suggest a package weight, a line's location only to find the ship-from address when the fulfillment has none, and the sales order's prices for the declared value when you turn that option on.

If your warehouse packs with PackShip in NetSuite WMS, NesoTMS can start the ship page with the cartons PackShip recorded, with their sizes and weights, when the sales order has just that one fulfillment and it isn't shipped yet. The ship page then says Boxes from PackShip.

With several fulfillments on the order, a carton can't be matched to one of them, so NesoTMS keeps the fulfillment's own package lines. A size PackShip doesn't have stays blank and is never guessed. Other warehouse systems work through the standard package lines on the fulfillment: if your system fills those, the boxes prefill.

A void goes to the carrier first, using the same carrier account and environment that bought the label. Only then does NesoTMS update NetSuite: it blanks that label's tracking numbers and, when no other active label is left, sets the status back to Packed. If the carrier refuses the void, the label stays active and NetSuite is not touched. FedEx Freight has no cancel service: an administrator cancels with FedEx Freight and records the carrier's confirmation in NesoTMS.

The NetSuite integration is part of every plan. Basic is $99/month and Advanced is $499/month; both have every shipping feature and differ only in how many users, warehouse locations, shipping stations and carrier accounts they include. There is no charge per label: labels are bought on your own carrier accounts and the carrier bills you. See pricing for the full comparison.

The interactive demo runs in your browser with made-up orders and rates, so you can try the ship flow without connecting anything. It never calls NetSuite. Before you connect says what the NesoTMS Connector role can do, Connect NetSuite has every step, and the Test connection button and the preview of your first 10 records show what your account returns before anything is turned on.