Explore AIMS360's apparel business software
FREE DEMO

Fleet Distribution Centers is a family-owned New Jersey 3PL serving the New York and New Jersey port region since 2003, with buildings in Monroe, Dayton and Harrison. AIMS360 connects to it as a stocking location: orders out, shipments and receipts back.

Fleet Distribution Centers logo
3PL integration · Fleet Distribution Centers

Fleet Distribution Centers 3PL integration: a New Jersey stocking location in your ERP

Fleet Distribution Centers is a family-owned 3PL that has served the New York and New Jersey port region since 2003, for importers, apparel brands, consumer goods companies and retailers. AIMS360 connects to it as one more stocking location, so containers received at Fleet become stock your East Coast customers can buy the same day.

AIMS360
Fleet Distribution Centers · New Jersey
2003
Serving the NY and NJ port region since
3
New Jersey buildings it lists
562,000
Square feet across the three, its figures
1
Stock record across every warehouse
The short answer

Does AIMS360 work with Fleet Distribution Centers?

Yes. Fleet Distribution Centers is a live AIMS360 3PL connection, run on the AIMS360 warehouse document set. AIMS360 sends 940 ship orders and 943 inbound advice, and Fleet sends back 945 shipment confirmations and 944 receipts. Every unit at Fleet sits on the same stock record as your other locations, by style, color and size.

Fleet's own site lists the 832, 940, 943, 944 and 945 among the EDI transactions it handles, and says it also connects by API. Which documents your account exchanges, and how, is agreed during setup.

At a glance

Fleet Distribution Centers at a glance

What Fleet publishes about itself. These are its facts, dated.

Topic Fleet Distribution Centers
Who Fleet Distribution Centers LLC, family-owned and owner-led since 2003.
Monroe, NJ 204,000 square feet, 27 dock doors, 27 foot clear height, conveyors and pallet racking.
Dayton, NJ 211,000 square feet, 34 dock doors, 28 foot clear height, very narrow aisle storage and conveyors for container unloading.
Harrison, NJ 147,000 square feet for warehousing, retail distribution, fulfillment and local transportation.
Services Receiving, pallet, carton and bulk storage, shipping and distribution, ecommerce fulfillment, value-added services, and transportation and drayage.
Systems Runs the Synapse warehouse management system with RF scanning from receiving to shipping, EDI, API and online reporting.

From Fleet Distribution Centers' own site, checked November 3, 2026. Building sizes are Fleet's figures.

What moves

What moves between AIMS360 and Fleet

The AIMS360 warehouse document set. The format column is how AIMS360 sends and reads each one.

Document Direction Format in AIMS360 What it does
832 style data AIMS360 to warehouse Tab delimited file Sends new styles to the warehouse: description, UPC, unit of measure, cost and, if you choose, wholesale price. The warehouse needs the same UPC or style, color and size codes before any order file moves.
940 ship order AIMS360 to warehouse AIMS360 standard XML Sends orders or pick tickets, your choice in system settings. Exported pick tickets move from Open to Packed, so nothing goes to the warehouse twice.
943 inbound advice AIMS360 to warehouse AIMS360 standard XML Tells the warehouse what is coming: a vendor PO, a cut ticket or a customer return, so the dock knows what to expect.
944 receipt Warehouse to AIMS360 AIMS360 standard CSV What the warehouse counted in, by UPC or by style, color and size. It posts against the open purchase order or return, and the units become stock.
945 shipment confirmation Warehouse to AIMS360 AIMS360 standard XML What shipped, with carrier and tracking. AIMS360 records the shipment, marks the pick ticket Shipped, and builds the invoice and, for EDI retailers, the 856 from it.
947 stock adjustment Warehouse to AIMS360 AIMS360 standard Excel template Adjusts stock up or down for a miscount, damage or mislabel, with a posting date and a note on why. It corrects a gap; it does not overwrite the count.

The numbers are shared warehouse vocabulary, not a promise of X12. In AIMS360 these messages travel as XML, CSV, tab delimited or Excel files on a file site the warehouse hosts or AIMS360 sets up, or as API calls for warehouses that work that way.

An order

One order through AIMS360 and Fleet, in six steps

The same path for a retailer order, a Shopify order or a wholesale order.

  1. The order lands in AIMS360

    From a retailer 850, Shopify, a B2B order or a marketplace. It allocates against one stock record by style, color and size, whichever warehouse holds the units.

  2. A pick ticket is created

    By hand, in a batch, or automatically for Shopify orders. If you send pick tickets rather than orders, you decide exactly which units ship, and the warehouse cannot fill from stock you are holding for another account.

  3. AIMS360 sends the 940 to Fleet

    The ship order goes out with the ship-to, the carrier and the order references. The pick ticket moves from Open to Packed, which stops anyone exporting it twice.

  4. Fleet picks, packs and ships

    The warehouse works the order in its own system and labels the cartons.

  5. The 945 comes back

    AIMS360 reads the carrier, matches each item by UPC or by style, color and size, and records the shipment. The pick ticket moves to Shipped.

  6. The paperwork goes out from AIMS360

    The invoice is built from the shipment. For an EDI retailer, AIMS360 sends the 856 and the 810 from the same record. For Shopify, fulfillment and tracking go back to the store.

01

Close to the port

Fleet serves the New York and New Jersey port region and runs drayage. Containers that land there reach a Fleet dock, get received on the 944, and show as stock in AIMS360 without a spreadsheet in between.

02

East Coast wholesale

Department store and specialty accounts in the Northeast get shorter transit from New Jersey. AIMS360 builds the retailer 856 and invoice from the 945, so the warehouse does not handle retailer EDI.

03

Next to a West Coast 3PL

Many brands pair an East Coast building with a West Coast one. Each is a stocking location in AIMS360 and allocation decides which ships each order. See multi-warehouse.

Setup

Connecting Fleet Distribution Centers to AIMS360, in order

Your AIMS360 implementation manager runs this with you and the warehouse.

  1. Agree the connection with Fleet

    Our implementation team confirms with the warehouse which documents it will exchange and how: files on a file site or API calls.

  2. Set up the warehouse in AIMS360

    Add Fleet as a warehouse location, point it at the file site or connection, and give your team the permissions they need.

  3. Line up item codes

    The same UPC or style, color and size codes must exist on both sides before files move. AIMS360 can send new styles as an 832; some warehouses load item data themselves.

  4. Map the carriers

    Each AIMS360 ship via code maps to the warehouse's carrier code, carrier name or shipping mode. On the way back, AIMS360 matches on the carrier code first, then the carrier name, then the service.

  5. Choose orders or pick tickets

    Decide what the 940 carries. Pick tickets give you control over exactly what ships. Change it later only after every exported pick ticket has shipped and its 945 is processed.

  6. Test a full cycle

    Run real orders out and shipment confirmations back, plus a receipt and a return, before a retailer order depends on it.

  7. Go live

    Orders route to Fleet from AIMS360 and confirmations come back. Your implementation manager watches the first weeks with you.

Fleet FAQ

Fleet Distribution Centers and AIMS360 questions, answered

Yes. Fleet is a live AIMS360 3PL connection, run on the AIMS360 warehouse document set: 940 ship orders and 943 inbound advice out, 945 shipment confirmations and 944 receipts back, on one stock record.

Fleet lists three New Jersey buildings: Monroe at 204,000 square feet, Dayton at 211,000 and Harrison at 147,000, as of November 2026. Confirm which one will hold your goods, because each can be its own stocking location in AIMS360.

Fleet says it runs the Synapse warehouse management system, with RF scanning through receiving, put-away, picking and shipping. AIMS360 stays your inventory of record; Synapse records what is physically on Fleet's shelves.

Both, according to its site, which lists the 832, 940, 943, 944 and 945 among its common EDI transactions. AIMS360 sends and reads warehouse messages as files or by API, so either works.

AIMS360. Fleet returns the 945 with the shipment, and AIMS360 builds the 856 and 810 from it. See EDI retailers.

Fleet offers ecommerce fulfillment. Shopify orders import into AIMS360, allocate, and go to Fleet on the 940; when the 945 comes back, AIMS360 sends fulfillment and tracking to Shopify.

Fleet describes itself as family-owned and owner-led since 2003. No sale or rename appears on its site as of November 2026.

Most 3PL connections move from scoping to go-live in weeks rather than months. Lining up item codes with the warehouse is usually the longest step.

AIMS360 builds and maintains 3PL connections in house. Whether it is included or an add-on depends on your plan; see pricing. Fleet bills its own warehouse services.

Storing goods at Fleet?

Bring a container and a week of orders. We will show the receipt, the ship order and the confirmation running through AIMS360 on your styles.