Several use cases is supported by AOF - as an example let's look at a retailer with these characteristics:
Multiple Brick and mortar stores
Supports: Buy Online Pickup In Store (BOPIS) and Delivery with multiple providers such as Uber or DoorDash.
No dedicated inventory for online orders. Picking happens at each physical store - directly from the shelves in each store.
This is a pretty common use-case, and one that fits well with AOF. There's fulfillment apps out there, but they obviously depends on having there own Product Catalog to work from. This often leads to these catalogs not being "in sync" - which leads to a lot of issues ending up in bad user experiences.
AOF is build on top of Sitecore OrderCloud - so a perfect match would be if your storefronts or B2B solution is built with OrderCloud. In this case - the Product Catalog is already there, and you will never experience problems having Product Catalogs being out of sync. On another front - there's most likely a large cost saving eliminating a 3rd party in-store fulfillment system.
In OrderCloud this setup would be modelled each physical store as a Supplier and each store employee as a Supplier User. When the Supplier User login to AOF, she/he will see orders that's ready to be picked in that given store.
Through the intuitive interface, the rest of this picking process will happen on the mobile device. As it's on a mobile devise there's quick function to scan Barcodes on products, calling the customer with a single click etc.
You might have special flows and special use-cases?
Not a problem.