When a person is checking that orders arrived somewhere, or when routing rules live in someone's head. One channel and one warehouse rarely justifies it. Two of either usually does.

An ERP is the system of record for finance and inventory. Order operations is the connective layer moving orders between channels and fulfilment in near real time. They complement each other, and Pipe17 often feeds the ERP rather than replacing anything in it.

That is the case worth designing for. Failures should surface immediately with enough context to fix them, not sit silently in a queue. We spend more implementation time on exception handling than on the happy path, because that is where the customer damage happens.

Yes, and that is a common reason to adopt it. The work is agreeing the rules, since deciding which location ships what is a commercial decision about cost and speed before it is a technical one.

Six to ten weeks for a multi-channel brand. Connecting systems is quick. Documenting how orders should actually flow, including the exceptions, is what takes the time and what determines whether it works.