StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16042183
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-16T16:23:36.383
FavoriteCount
0
LastActivityDate
2013-04-16T16:23:36.383
LastEditDate
LastEditorUserId
0
OwnerUserId
730127
ParentId
15943864
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You may or may not like this, but I have warehousing and order fulfillment processing experience. My personal real life experience didn't require an algo but a series of warehouse and customer service back tools (hopefully this will be food for thought to you and others struggling in the warehousing operations development world): If you have 10 items on the order. You have 9 in stock You have 5 in one location and 4 in the other. You split the order. The 1 product that can't be fulfilled becomes a 'back order'. It can be cancelled because you don't know when you or if your supplier is going to deliver. Make sure you hang on to your credit card authorization references. The 9 left over (fulfill-able products) in stock will be queried against your warehousing virtual inventory for the best combinations. In our case we do three things: Can the fulfillment staff at a warehouse X transfer in the item from another warehouse easily? Yes/No If so which products can transfer. This might require human interaction based on warehouse load and capabilities. If you are strictly going on automation and virtual inventory that fluctuates day in and day out, then you give it your best guess against warehouse inventories. Next, split the order to two, with references to the main order for paper trails. You then print to your destinations and hope they can fulfill, if they can't, then hopefully they can partially fulfill the order and generate back order that can be cancelled at the customer's request. So basically here is what you have to code for. Order First glance back order split and reference to main order. Inventory warehouse feeler function. Weighted split order based on virtual inventory with reference to main order based on warehouse capabilities to retrieve products from other warehouses. Print pick page (warehouse function) Back order or partial fulfillment manual functions (customer service tools) Collect the money on only the stuff you fulfilled when marked as shipped. Considerations: Make sure the main order references the actions back order and splits. Make sure the splits and partial fulfillment orders references any additional back order and splits. Fullfill what you can Mark a shipped. Collect $$$ on the products that shipped. Hope this helps and good luck!!!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOptimal order fulfillment
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFrank Tudor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.