Today in Acumatica, when Sales Orders are processed into Shipments, the system will by default process based on a limited set of available filters at the Sales Order document level. This method involves the assignment of inventory (SKU’s) generally based on the date ordered. SKU’s that are not available may be back ordered and processed into a separate shipment at a later date. This method appears to assume that all SKU’s on any given order are available or will be available in the short term to fill all open orders. It also appears to assume that companies who wish to capture payment prior to shipment would process the payment on the Sales Order regardless of which items may have been shipped or back ordered.
Example scenarios where the current process may fall short.
- Companies engaged in B2B and B2C sales where priority may be given to one customer type over the other based on a variety of variables.
- Companies selling limited availability items which need to be distributed across the customer base.
- Companies whose customers may place multiple orders for a variety of SKU’s.
- Companies taking pre-orders with specific distribution rules enforced by the manufacturer (may ship to retailers but not end consumers until a designated release date).
- Companies selling internationally where dollar value and weight may play a role in what can be included in a single shipment.
- Companies selling to customers using multiple credit cards to purchase inventory with pre-defined limits on what can be charged to a given card.
- Companies that require full payment (Capture) prior to shipment, allow multiple orders within a single shipment and do not have all SKU’s available in inventory all of the time.
Proposed enhancements to facilitate stronger user control over customer priority and SKU assignment.
I understand we can create customizations to address many of these requests. Having a pre-built process will make it much easier for the end users and better facilitate the needs of ecommerce companies.
- Create a Generic Inquiry (GI) driven process to update the Order Priority field on the Customer screen (AR.30.30.00) | Shipping tab.
- Create a Generic Inquiry (GI) driven process to update the Priority on individual Sales Orders (SO.30.10.00) under the Shipping Settings tab.
- Modify the Process Orders (SO.50.10.00), Action | Create Shipment to utilize a Generic Inquiry (GI) as the basis for transactions to be processed.
- Modify the Process Orders (SO.50.10.00), Action | Create Shipment for Order Types that do not require ‘Ship Separately’ to process at a Sales Order Line Level rather than an order level.
- Modify the Process Orders (SO.50.10.00), Action | Create Shipment using Generic Inquiry (GI) as the source for transactions to process to override Sales Order line ‘Quantity to Ship’ and utilize this value in the process of creating the shipment. The remainder on the Sales Order Quantity would be Back Ordered.
- Modify the Shipments screen (SO.30.20.00) to facilitate the Authorization and Capture of credit card payments.
- Facilitate the easy creation of additional Shipment Status settings to indicate company specific values and stages. (Examples: Pending Review, Pending Payment, Picked, etc.).
- Facilitate the bulk update of user defined Shipment Status based on a Generic Inquire (GI).
I look forward to reading contributions from the Acumatica Community on this topic.
Best answer by josh.fischerView original