Other Considerations of Remote Operation

• Remotes should avoid layaway transactions. Because layaways are an oddball in terms of point of sale processing in that they may potentially be accessed and updated many times in the course of their existence, they can cause inconsistencies between a remote and the office system. Unless the remote uses layaways only so that they are created and completed within one period, we highly recommend that you not use them. The remote capability was not developed with any special capabilities for layways.
  
  
• The merging process used for detached operation makes some attempt to determine if there are incompatibilities between the remote files and office files (primarily references to information in remote transactions found missing in the office system) and will report these problems so that they can be dealt with. However, in independent operation there is no opportunity for these checks. Thus especially when used in this mode it is extremely important that the office system not make important changes to Inventory or Accounts Receivable data (like deleting customers, items, and so on) while the remote is in operation. Whenever possible reserve these activities for when the remote is inactive so that current AR and IN files can be provided to the remote before they continue processing.
  
  
• Remotes that are merged (detached operation) do not have their till information transferred to the main PI company. Till reconciliations should be completed before merging.
  
  
• Never set detached and independent remote companies for real-time updating in Utilities … System Defaults. This will short-circuit the entire remote process and all transactions will never be updated to the main office’s Accounts Receivable and Inventory companies.