| Ravi Shankar 2006-02-17, 10:50 pm |
| Hi sshier,
If you're treating order confirmation as inventory commitment then you have
another option.
In this option you can maintain the allocated inventory & qty on hand as a
Commerce Server Resource (meaning basically as a table in CS). You can keep
decrementing the qty on hand with every confirmation and increment it on
order cancellation. Once (beginning of day) you can replace the CS table with
the Actual Stock figures from the backend ERP. This way your inventory
calculation does not have to incur a external system call.
--
Ravi Shankar
"sshier" wrote:
[vbcol=seagreen]
> Thank you Ravi, Colin and Jeff.
> I agree with you Ravi that an XML/Web Services integration into a pipeline
> component might be best and had thought of the same basic approach.
>
> When an order is placed it is considered "committed" which means that its
> not available to sell. When it is shipped/picklisted is when it is
> decremented from inventory permanently. In that way, cancellations can put
> the order back into inventory.
>
> Our concern with the MSCS2002/BT2004 solution was a few extra weeks of
> development and the weaker MSCS2002 product feature set compared to the
> MSCS2006 product. As such we are using the ERP's commerce system for now and
> will have to do this switch later. In the meantime, we plan to use BT2004 or
> 2006 for the Amazon integration with the ERP back end.
>
> Thanks again for all your help.
> --
> Steve Shier
>
>
> "Ravi Shankar" wrote:
>
|