Jet Distribution Services in Teterboro, New Jersey, connected to AIMS360 across six warehouse documents. The catalog regenerates nightly for any style newly assigned a UPC, inbound advice converts every ten minutes, and an inventory adjustment from the warehouse triggers an automated stock discrepancy report.
Most 3PL pages talk about parcels. This one has to talk about rail, because Jet Distribution publishes more than 20,000 feet of garment on hanger rail alongside its flat pack operation, plus pressing, steam cleaning, ticketing and tagging. If your product arrives on hangers and has to leave on hangers, that changes which warehouses are actually candidates.
Six warehouse documents run live, in both directions, over SFTP. The file transport is hosted on the Extensiv platform that Jet runs its warehouse on, so there is no middleware server sitting between the two of you that somebody has to own.
| Document | Direction | What it carries |
|---|---|---|
| 832 | AIMS360 to warehouse | The product catalog. Style, color, size, UPC and description, so receiving is never guessing at a SKU |
| 940 | AIMS360 to warehouse | The ship order, serving as either order or pick ticket depending on a system setting, carrying the pick number and the customer purchase order |
| 943 | AIMS360 to warehouse | Inbound advice. What is arriving from production or another location, and what to expect on the container |
| 944 | Warehouse to AIMS360 | The receipt, posting against the open purchase order or return line so on hand moves without a receiving sheet being keyed |
| 945 | Warehouse to AIMS360 | Shipment confirmation with carton detail, weights and tracking. The carton structure is what lets AIMS360 generate the retailer 856 advance ship notice |
| 947 | Warehouse to AIMS360 | Inventory adjustment. Damages, cycle count corrections and found stock, and the trigger for the discrepancy report below |
Six rather than seven. There is no periodic inventory snapshot on this connection, which is worth knowing rather than glossing over, and we cover what that means in the limitations below.
Two warehouses can support identical document lists and feel completely different to work with, because the thing that matters day to day is not which documents exist but how often they move. Here is what runs on this connection.
A 943 raised in AIMS360 is converted and delivered on a ten minute cycle. Raise the advice, go and do something else, and the warehouse has it before you have finished the something else.
The 944 poller runs every hour, so a container received in the morning shows as on hand in AIMS360 the same morning rather than the next day.
The 832 regenerates overnight for any style newly assigned a UPC. Nobody remembers to send it, because nobody has to.
A 947 arriving from the warehouse triggers an automated stock discrepancy report rather than landing silently in a transaction log.
A failed conversion leaves the original file in place for correction and reprocessing rather than dropping it. That sounds like a small thing until the first time a file fails at 4pm on a Friday.
Here is the failure it prevents. A style gets a UPC assigned on Tuesday because a retailer needs it. Goods for that style arrive at the warehouse on Thursday. If the warehouse catalog was last sent in March, the receiving team has a carton of product with a barcode their system does not recognize, and the choice is to guess, to call you, or to put it aside. All three cost a day.
On this connection the 832 regenerates overnight for anything newly assigned a UPC, so the warehouse catalog is never more than a day behind your product data. It is a small piece of automation that quietly removes an entire category of receiving exception, and it is the kind of thing that only shows up in a comparison if somebody asks the right question in a demo.
Ask it. "When a style gets a new UPC today, when does the warehouse know?" The answers you will hear range from overnight to whenever somebody exports a spreadsheet.
Plenty of ecommerce 3PLs handle apparel in the sense that they can put a folded shirt in a poly mailer. Fewer can take goods off a container on hangers, keep them on hangers through storage, press or steam them, ticket them to a retailer's spec and ship them on rail. Jet publishes all of it.
From their own site: more than 20,000 feet of garment on hanger rail and more than 15,000 bin locations, flat pack distribution alongside GOH, pressing and steam cleaning, label application, tagging and ticketing, poly bundling for pre-packs, plastic heat shrinking, display assembly and kitting, returns processing with quality control alerts, segregated and clean room storage, cycle counts, cross docking, and inbound handling across LTL, LCL, FCL and air with a rail siding on site.
The AIMS360 side of that is the part people forget: ticketing to a retailer's spec depends on the warehouse holding accurate style, color and size data, which is what the 832 is for, and shipping on rail still has to produce carton level detail on the 945 so the 856 going to the retailer is right. Hanging goods do not get an exemption from compliance.
Last reviewed 15 August 2026 by the AIMS360 integrations team.
Integration status and cadence reviewed against the AIMS360 production configuration for this partner. Company facts checked against jetwarehouse.com in August 2026 and attributed to the publisher rather than stated as our own.
Everything here comes from Jet's own website, attributed rather than repeated as fact. One caveat we would rather state than hide: their site carries a copyright line ending in 2013 and its square footage figures do not agree with each other across pages. Confirm current numbers with them directly rather than from us or from a directory.
| What they publish | Detail |
|---|---|
| Company | JET Distribution Services Inc., founded 1984 |
| Location | Teterboro, New Jersey. No second facility is published |
| Building | A 102,500 square foot main building with 50 foot clear height. Larger network totals appear elsewhere on their site and do not reconcile, so treat any total as approximate |
| Storage | More than 12,000 pallet positions, more than 15,000 bin locations, more than 20,000 feet of GOH rail |
| Apparel handling | GOH and flat pack distribution, pressing and steam cleaning, label application, tagging and ticketing, poly bundling, heat shrinking |
| Other services | Pick and pack fulfillment, returns processing with quality control alerts, display assembly and kitting, cycle counts, crating and banding, cross docking |
| Inbound | LTL, LCL, FCL and air, import and export handling, rail siding on site |
| Security | In rack sprinklers, 24 hour CCTV, central station monitoring |
| Integration approach | They describe connecting their warehouse system to order and inventory systems from small accounting packages up to full ERP, over FTP, API and EDI |
| Not published | Client count, named carriers, certifications, and named retailer compliance programs |
A naming note, because search confuses these constantly. The AIMS360 partner is the Teterboro, New Jersey company at jetwarehouse.com. It is not Jet Fulfillment Services in Ball Ground, Georgia, which also serves apparel brands, and it is not Jet Delivery, Jet Logistics or Cargo Jet Logistics.
There is no periodic inventory snapshot. Some of our warehouse connections carry an 846, which is a full position from the warehouse that you can reconcile against. This one does not. Adjustments arrive on the 947 and trigger a discrepancy report, which catches drift as it happens, but if you want a scheduled full count comparison you will be arranging it separately.
Cancelling a released pick ticket is a manual step. Once an order has gone to the warehouse, pulling it back is a phone call rather than a button. That is true of most warehouses on our list.
Their published information is dated. We are comfortable with the integration because we run it. We are less comfortable vouching for square footage on a website that has not been substantially refreshed in years. Ask them.
Yes, and it is live rather than in development. Six warehouse documents run in both directions over SFTP: the catalog, ship orders and inbound advice going out, and receipts, shipment confirmations and inventory adjustments coming back. Inbound advice converts on a ten minute cycle, receipts are polled hourly, and the catalog regenerates overnight for any style newly assigned a UPC.
Some can, most cannot, and it is the single fastest way to shorten a warehouse shortlist. Handling GOH means rail in the building, hanging storage, and the ability to press or steam before shipping. Jet publishes more than 20,000 feet of GOH rail plus pressing and steam cleaning alongside its flat pack operation. If your product ships on hangers, ask every warehouse on your list for their rail footage before you ask about anything else.
On this connection, overnight. The 832 product catalog regenerates for any style newly assigned a UPC, so the warehouse catalog is never more than a day behind your product data and receiving does not meet a barcode its system has never seen. It is worth asking the same question of every warehouse and every ERP you evaluate, because the honest answers range from nightly to whenever somebody exports a spreadsheet.
The warehouse sends an inventory adjustment on the 947 and AIMS360 triggers an automated stock discrepancy report, so the difference surfaces as a document rather than as a surprise at the next count. What this connection does not carry is a periodic full inventory snapshot, so if you want a scheduled position to position comparison you will arrange that separately with the warehouse.
No, and the split matters. The retailer documents stay with AIMS360: the 850 comes in, the 855, 856 and 810 go back on the retailer's routing guide spec. The warehouse documents are separate. The join between them is the carton detail on the 945 coming back from the warehouse, which is what the 856 advance ship notice is built from. Get that right and compliance is unaffected by where the goods sit.
Yes. In AIMS360 every physical location is a warehouse, including your own building, your retail stores and each 3PL, so several can be live at once on the same stock record. Inventory templates decide what each location can sell and routing decides where an order ships from. Adding a warehouse is adding a location, not adding a system.
Bring an order and a purchase order. We will send the ship order, take the confirmation back with carton detail, and show you the advance ship notice it produces.
