Sage 100

v2014 Std. Client has two companies - The main one and a web site shell company. In the process of moving the shell company out of QB into Sage. SO Order is entered in main company (ACS multi bin) and shipped to web site customer. Order is also enter into web site company as a SO to customer AND as a PO to main company for processing. Looking for ways to minimize/eliminate the duplicate entry. Transactional volume is between 35 - 50 orders per week. One or two lines per order. 1) Enter SO in web site company as a drop ship and eliminate the PO entry entirely? Only one COGS account in web site company. 2) Enter SO in web site company and auto generate the PO? 3) Some sort of VI to import data into web company? 4) SO BOI Script that would pull the data from the main company and populate the web site SO? Anyone know of 3rd party enhancements? We discussed using one company with divisions and departments, but owner thought this might be too complicated, plus companies are separate legal entities (not that really matters). A additional stumbling block with one company is credit card processing. We don't want the CC details sent to end customer to reflect the Main company's name on the CC paperwork.

Jeff, what about something like this? 1) Enter (import) a sales order into Web Co from Web Site including credit card info along with a new customer record 2) All items on order are drop ship from Parent Company vendor 3) Create PO in Web Co for Drop Ship items following standard 100 procedures 4) Execute an export of drop ship SO's in Web Co as a data source for a VI job in Parent Co 5) Execute a VI job to import SO's into the Parent Co with the ship to address as the end customer and Web Co as the customer 6) When goods are shipped in Parent Co, create an export that can be the data source for a PO Receipt of Goods and/or Receipt of Invoice VI job in Web Co 7) Execute a VI job to import PO Receipt of Invoices into Web Co 8) Follow the standard drop ship invoicing routine in Web Co to receive goods, invoice the customer, and collect on the credit card. The above depends upon an export and an import VI job for two processes; 1) Receipt of Sales Order, and 2) Shipment of Goods. You can't chain the export and import jobs across companies (I don't think you can at least) but you can automatically execute each from within Access. I would also recommend adding a UDF on the Sales Order in Web Co and on the Shipment in Parent Co that you can set via another pair of VI Jobs to let you know transactions have been exported to the related company. This way they don't get exported multiple times. (Maybe set an export date in case you need to compare it to the last update date on the head record tag.

Sorry, re-read your request. Use the same process as above only reverse the source and target companies. Create the order in the Parent Co, then bring in all the items on the order either as * items or as miscellaneous items so you can avoid maintaining any inventory in Web Co. (This avoids the need for a PO in Web Co.) You can still make all the sales in the Parent company be to Web Co as the customer with shipping addresses as the end customer. However, you will have to maintain two sets of invoice formats and two sets of packing slips unless you add logic to your forms to change the header info dynamically based upon the customer ID. If the customer is Web Co, use format B. If the customer is not Web Co, use format A. This still won't get you around the name on the credit card transaction on the customers CC statement. The only way I can see around that is to bill the card from the Web Company instead. (On the plus side, this will negate the multi-format invoice issue.

@ShawnSlavin - Thanks for the thoughts. Given the limited number of daily transactions and the limited number of lines on each order and how they flow into for processing, I struggle with the efficiency of the importing/exporting. I will run the scenarios by the client for input. They do like having the part number in the web company. I might be able to convince them to drop ship the items. All depends on what their pain points are. BTW, a number of years ago I had a client doing similar importing and exporting. Setting up a UDF to indicate that the order had been exported/uploaded was a time saver. great idea.