Answer
Start by walking the floor with the people who will use the system daily, not just the operations manager, and write down every device, label format, and carrier requirement that shows up in a normal week. A warehouse that ships both small parcel and LTL freight needs label logic and packing workflows that a scanner vendor built primarily for parcel shippers may not handle cleanly, and that gap rarely shows up until the first real freight shipment goes out wrong.
Ask vendors directly whether their platform supports your specific carriers' label formats natively or requires a third-party label engine bolted on, since that affects both cost and long-term maintenance. Wireless constraints deserve the same attention: a facility with metal racking, cold storage, or a large physical footprint can create dead zones that a vendor's standard access point count will not cover. Before signing anything, insist on a proof-of-concept scan event using your actual devices, your actual labels, and a workflow that includes a carrier handoff, not a vendor's polished demo environment with ideal signal and pre-staged data.