Knowledge Base

Release 18.02.15 DB Version 161

Updated on

------------ Release Update 18.02.15 DB Version 161 ----------------


EDI


  • EDI Backorder codes “B” and “Z” have been added to the Send Order screen.
  • Code “B” is defined by Pubnet as Backorder only if New.
  • Code “Z” is a Penguin Random House specific code for Backorder Hot and Not Yet Published (NYP) titles only.


Front List / PO Import


  • When adding a new product, the publisher and vendor fields can now be different.
  • Previous releases forced the publisher to be the same as the vendor.
  • [i]merchant will use the Import_PubCode field for the publisher.
  • The Import_PubCode field must be a valid [i]merchant Vendor Short Name.
  • If [i]merchant does not find a valid publisher, the publisher will be set to the same value as the vendor.


Store Properties / Texting


  • A Twilio phone number has been added to the General tab of store properties.
  • If a store specific phone number is not configured, [i]merchant will use the Twilio default phone number in the Twilio setup section of system options.
  • A new field has been added to the bottom of the text message form showing the showing the store that will be used when sending the message.
  • When sending customer order notifications, [i]merchant will use the phone associated with the store that took the customer order.



Cost Profit Compare / Sales Analysis Compare Reports


  • When exporting a totals only report to a CSV file, the second period data did not line up properly with the headings.

PO Report


  • The PO vendor field was added to the report




Cost Profit Summary Report


  • Under some conditions multiple rows for the same information would be displayed.
  • Add Cost/On Hand and life total fields to grouping.
  • Department category group has been added to the report pallet,

Receiving / Receiving Summary Reports

  • Order and received margin columns were added to the report.

Receiving Summary Report

  • A version of the receiving report allowing the user to summarize receiving information based on the fields selected.
  • Instead of showing product level detail, this report add together tot amounts based on the fields selected for the report.
  • This report can be used to get a total order and received for a vendor, or group of like products.


Transfers

  • When creating a transfer PO, the transfer quantity will be adjusted so the on hand in the sending store is not exceeded.

 Po Finders

  • A PO Number ending option has been added to the search forms that find by PO number.

Advanced Finders

  • An “Ends with” option has been added to the list of operators.

Finders

  • A “Select All” option was added to the edit menu.
  • Control-A key can be used as a shortcut for the select all option.


POS Transaction Finders

  • The “Txn Date” fields have been renamed “Sale Date” to be consistent with the other POS reports and inquiries.
  • A “Sale Date” has been added to the field selection list making it easier to select a single sale date. Previously the “Txn From” and “Txn To” fields were needed.


System Options

  • The POS tab has a check box option to display a message if a customer previously purchased the same product.
  • POS checks for the product against all stores and items.
  • The previous sale date information is displayed on the product detail area on the top of the form.


POS

  • A Computac option was added to disable doing a product lookup.
  • When PLU is disabled, POS will prompt for the price if the price was not found in the barcode.
  • If the PLU price is lower than the barcode price POS will use the PLU price.
  • POS will always use the sale price of an item and shows the LU price as the regular price.
  • Importing a customer order will use the PLU price.


  • Behavior of the Not On File prompt has changed.
  • The user must click on a button or press enter to move from the NOF prompt.
  • In previous releases, if the cashier did not check the screen, scanning the next product accepted the screen.


  • A check was added to prevent a sale from accepting an A/R payment and using the same A/R account in a single sale.


Vendor Policy


  • The quantity column can now be used in a product type, or binding type discount schedule.
  • Existing entries will assume a quantity of 1

Purchasing Agent


  • The vendor minimum requirement check was changed.
  • Previous versions set the Meet Minimum false when the vendor minimum quantity and minimum dollars were set to zero.


Previous Article Release 18.04.09d DB Version 162
Next Article Release 18.07.17e DB Version 165
Still Need Help? Contact Us