fba-logistics-select

You can automate Amazon FBA logistics selection by providing a TSV input with consignment_no, shipment_no, and destination_address columns, then running a fixed CLI to map the data to local box files and determine the optimal shipping route.

FBA logistics optimization via CLI requires a TSV input containing exactly three tab-separated columns: consignment_no, shipment_no, and destination_address. The system validates batch consistency and ensures all shipment numbers are unique before processing.

The FBA logistics CLI maps shipment identifiers by locating corresponding box files named {consignment_no}.xls(x) within the artifacts/mabang_wms_consignment directory, using the validated TSV input to match consignment numbers with their packing data.

FBA logistics batch selection fails during validation if the TSV input lacks the three required tab-separated columns, contains duplicate shipment numbers, or has inconsistent batch data that prevents accurate mapping to the local box files.

No, you cannot use a different file format instead of TSV for FBA shipment logistics selection because the fixed CLI strictly requires a TSV input to validate batch consistency and unique shipment numbers before mapping to the box files.

The best way to handle FBA logistics selection for large shipment batches is to compile all consignment and shipment identifiers into a single TSV file, allowing the fixed CLI to automatically validate batch consistency and map entries to their respective box files.