It started with a problem.
Moving heavy goods in warehouses and between vehicles was physical work before the pallet. Workers carried, rolled, or slid individual items. The pallet — a flat wooden platform sized to be lifted by a forklift — enabled a single operator with a fork truck to move large loads quickly. The forklift and the pallet developed together in the 1920s and 1930s, but widespread adoption accelerated dramatically during World War II, when the U.S. military needed to move massive quantities of supplies efficiently. The military's use of standardized pallets and forklifts created a logistics infrastructure that carried over into civilian use after the war.
Historical sources below ↓Then something changed.
The key shift was standardization. When pallets became a consistent size — 40 by 48 inches became the most common in North America — warehouses, trucks, and loading docks could all be designed around a known unit. A manufacturer who built its warehouse around the standard pallet could load goods onto a truck from another company, delivered to a retailer's warehouse, without any measurement or special arrangement. The common platform made each individual transfer cheaper. This network effect meant that departing from the standard became increasingly costly even for firms that might have preferred a different size.
What a builder can learn.
Our interpretation: the pallet's value came from its role as a shared physical standard. Any individual company could have designed a more efficient pallet for its specific operations. The value came from all companies using the same one. This is a lesson in platform economics: the private benefit of optimization is often less than the collective benefit of interoperability. For a small business that operates within a supply chain, understanding which standards are worth joining — and which are local inventions that create friction at every handoff — is a form of competitive awareness.
A door still open.
A hypothesis worth testing: if a small business identified one specification — a file format, a data field, a packaging size — that it currently uses internally but that differs from what its main partners use, what would the actual cost be of switching to the common format, and how would that compare to the cost of translation at every handoff?
What is the equivalent of the non-standard pallet in your business — a format or specification you chose independently that creates translation work every time it touches another system?
Follow the evidence.
History is sourced below. Business lessons are editorial interpretations; future possibilities are questions to test, not predictions.
Prepared from primary-source histories. First edition: 25 Sept 2026.