Help & frequently asked questions

WMS NextG is a warehouse management platform for third-party logistics. One system covers the warehouse floor (receiving, putaway, picking, packing, shipping), the freight desk (parcel labels, multi-broker LTL rate shopping, bills of lading) and a client portal that merchants log into themselves. It is built and operated by NJ Warehouse Express LLC and runs its own warehouses every day.

Operators are warehouse staff — receivers, pickers, packers, the freight desk, billing and management. They work in the full system.

Clients are the merchants whose goods are stored and shipped. They sign in to the client portal and see only their own inventory, orders, documents and invoices. The separation is enforced in the data layer, not just in the interface.

Accounts are provisioned by us — there is no self-service sign-up, because every account is tied to a real warehouse agreement and a real set of rates. Request a demo or email integration@wmsnextg.com and we will set one up. Existing users sign in at https://app.wmsnextg.com/login.

The web application needs nothing but a current browser — Chrome, Edge, Safari or Firefox. Nothing is installed on the desktop except an optional local print helper when you want one-click label printing to a thermal printer.

On the floor there is a companion Android application for handheld scanners (PDAs), used for receiving, putaway, picking, pallet building and Bluetooth label printing. The interface is available in English and Simplified Chinese.

The platform has built-in connectors for Temu, TikTok Shop, eBay, WooCommerce, Shopify, Amazon and Walmart, plus a REST API and a spreadsheet import for anything without a connector.

Whether an individual channel is available to your account also depends on that marketplace's own app-review status, which is outside our control. Ask us what is live for you today rather than assuming from this list.

Once your account exists:

• Open Integrations and choose Add integration.
• Pick the channel, name the connection, and choose which client it belongs to.
• You are sent to the marketplace's own sign-in page to authorize access. We never see or store your marketplace password — authorization comes back to us as a token.
• We register for order notifications and run an initial sweep for recent orders.
• Map any product codes that do not already match a SKU in the system.

A connection can be tested from the integration's own page, which shows the last sweep, the last notification received, and any errors with the reason attached.

Only what fulfilment needs:

• Read orders — to know what to pick, and where to send it.
• Read products — to match the marketplace's item codes to the stock on our racks.
• Write fulfilment — to send the carrier and tracking number back once the parcel leaves, and to pull a marketplace-issued shipping label where the marketplace provides one.

We do not request access to payouts, advertising, messaging or storefront content. Authorization tokens are held encrypted and are used only for the account that granted them.

Multiple stores, and multiple channels per client, are normal — each connection is separate and can be paused on its own.

Connecting the same shop twice is not recommended. Marketplaces generally key an order-notification subscription to the shop, so a second connection silently takes the first one's place and orders stop arriving on the original. If you need to move a shop to a different client, ask us to re-point the existing connection.

Deactivate the integration to stop importing immediately, or delete it to remove the stored authorization. You can also revoke our access from the marketplace's own developer or seller settings, which has the same effect from the other side.

Orders already received stay in the system as fulfilment records, because we have to be able to answer for what we shipped. The buyer's personal details in them are purged on the schedule below — see Data & security.

Where the marketplace supports notifications, an order appears within seconds of becoming shippable. A scheduled sweep also runs on a short interval as a backstop, so a notification that is delayed or dropped by the marketplace does not mean a lost order. Both paths land in the same place and neither can import the same order twice.

Usually one of these, and the integration's page will say which:

• It is not shippable yet. Unpaid orders, and orders still inside a marketplace's buyer-cancellation window, are deliberately not imported — picking them would mean picking orders that are about to vanish.
• A product code does not match. The order lands in Needs Review with the unrecognised code shown. Map it once and it imports; later orders match on their own.
• The connection needs re-authorizing. Tokens expire and marketplaces occasionally invalidate them. The integration shows the error and reconnecting fixes it.

Where the marketplace issues the label, we use the marketplace's label — you keep the platform's shipping rate, and the tracking number is the one the marketplace already expects. Where it does not, we buy the label, rate-shopping across the carriers and services configured for that account.

Larger consignments go out as freight instead: see Freight.

Yes, when the connection is set to push fulfilment. Marking an order shipped sends the carrier and tracking number back to the channel it came from, so the buyer's notification comes from the marketplace as usual. If the marketplace supplied the label, it already holds the tracking number and we confirm the shipment instead.

A push that fails is retried and surfaced as an error against the order rather than being swallowed — you can see it, and re-send it.

An order cancelled before it is picked is closed out and any reserved stock is released back to available. Once a parcel has shipped, cancellation is between the buyer and the marketplace; goods physically returned to the warehouse are received back against the original order so the stock and the paperwork agree.

Everything is scanned. Stock is tracked by SKU, by pallet, by carton and by location, and the portal shows the same numbers the floor sees. On hand is everything physically present; available is what is left after stock already committed to an order is reserved, which is the number that matters when you are deciding what you can sell.

Yes. Stock carries lot numbers where you use them, picking follows first-in-first-out by default, and an order line that names a specific lot is treated as a hard constraint — it will not be satisfied from another lot. Lot numbers print on the pick ticket so the picker is working from the same information.

Freight orders are quoted across several brokers at once, so you are choosing between real rates rather than one. Accessorials, freight class, NMFC and whether pallets are stackable all go into the quote and onto the bill of lading, because a quote that omits them is a quote you cannot actually book. Booking tenders the shipment, records the PRO number and produces the BOL and pallet build sheet the dock needs.

Yes — prep, carton marks, pallet labels and the build sheet are all supported, along with cross-docking a container straight onto an outbound trailer without putting it away first.

Their own inventory by SKU, pallet and carton; their inbound shipments and containers; their orders and shipments with tracking; their documents; and their invoices and charges. They can export any of it.

They cannot see another client's anything, warehouse-internal locations, or what the warehouse paid a carrier or broker. Permissions are per-role and per-user, so a client can give a colleague read-only access without giving away billing.

For a parcel going to a consumer we need the recipient's name, shipping address and, where the carrier requires it, a phone number or email. That is what a label needs. We process it on behalf of the merchant, for fulfilment and the customer service attached to it — never to market to anyone, and never sold.

We collect no payment card details at all; marketplace payments never pass through us. Full detail is in the Privacy & Data Protection policy.

For orders from a connected marketplace, buyer personal data is purged or anonymized within 30 days of shipment by a scheduled job — name, street, city, postcode, phone and email are removed from the order record.

What remains is the non-identifying fulfilment history we are required to keep: order reference, items, quantities, status, tracking number, timestamps, and the destination state and country for volume reporting. If an address is needed again for a return or a reprint, it is re-fetched from the marketplace at that moment rather than kept on the chance that it might be.

Yes, both ways. In transit, everything is HTTPS/TLS — the public site, the application, the API and every marketplace call. At rest, the database, its automated backups and snapshots, and document and label storage are all encrypted with AES-256 using managed keys, and credentials and marketplace tokens are held in a dedicated encrypted secrets store rather than in configuration files.

Hosting is Amazon Web Services in the United States (Ohio region). There are no servers in an office.

Access is role-based and least-privilege: a picker sees the pick queue, not billing. Client accounts are scoped to their own records in the data layer, so isolation does not depend on a screen remembering to filter. Administrative actions — voiding a charge, changing a status, signing in as another user — are written to an activity log with who did it and when.

Only where the shipment requires it: the carrier or freight broker that carries the parcel needs the delivery address, and our cloud infrastructure provider hosts the system. We do not sell data, and we do not share it for advertising. The current list is maintained in the Privacy & Data Protection policy.

Email integration@wmsnextg.com with enough detail to identify the records. Where we hold the data on a merchant's behalf we will confirm the request with that merchant first, since it is their data and their obligation we are acting under. Anything we are legally required to retain — tax records, for example — is kept for the statutory period with personal detail minimized.

• Email — integration@wmsnextg.com. Best for anything involving an order number or a screenshot, and the fastest route to whoever can actually fix it.
• Phone — +1 (862) 231-1336, for anything holding up a truck or a shipment.

We aim to answer within one business day, and the same day for anything stopping shipments from going out.

Four things make almost every integration problem quick to diagnose:

• The channel and store name as it appears on the Integrations page.
• The marketplace's own order number for an affected order.
• What you expected to happen, and what happened instead.
• When you first noticed it — roughly is fine.

Every import, label fetch and fulfilment push is logged against the integration with its outcome, so with an order number we can usually tell you what happened without needing access to your marketplace account.

Email integration@wmsnextg.com with the details and mark it as a security report. Please do not test against production data belonging to other merchants. We will confirm receipt and tell you what we find.