Whenever I am ordering components for some project I put them in a project tracker. A line might be like:
Order and Receive 5 Boxes
Request and Pick up the Check
When writing code to do networking you also have this problem. You have some code to "request" some data, and then you have code to handle what happens if the data doesn't come through. But on top of that there is a function that hides all that complexity and just "____"s the data.
Obtain, requisition, and acquire are all decent solutions to this problem. The problem is that they don't explicitly contain within them the idea that the task is both started and completed within the scope of this single word.
Requisition is much more like a request that has a high probability of success. Obtain and acquire certainly have a connotation of success and completion, but without the idea of the process that precedes them.
Those words are also a bit erudite.
Compound words are probably fine as long as they are normal use. Phrases are less good but maybe ok.
I have taken to using the made up word carg for this (because to me it sounds a bit like both cargo and the Spanish word encargar, which means to place in charge). But it turns out you can't expect others to know your private made up words.
Any other ideas? :)