Skip to main content

Purchase Inbound

Where: Settings › Generic Settings › Purchase and Other Payment › Purchase Inbound

Auto-update Product's Purchase Price after approving of Transaction​

Choices: Tick Update Purchase Price (then choose Current Branch, All Branches or Current Branch and ALL branches that copied from it), and/or Update Supplier's Purchase Price

What happens to the product cost when a purchase inbound is approved with a price different from the product's current purchase price:

  • Nothing ticked: costs are not updated.
  • Update Purchase Price: on approval, a window lists the products whose price changed. Tick the ones to update and CIRMS changes the purchase price in the current branch, in all branches, or in the current branch and every branch that copies its price from it. You can also approve without updating.
  • Update Supplier's Purchase Price: the supplier's purchase price on the product is updated too.

Only users with Purchase and Other Expense › Purchase Inbound › Auto-update Cost can update costs. In a branch other than the main branch, users with Purchase and Other Expense › Purchase Inbound › Create Price Adjust Request can create a Price Adjustment Request from the window instead. With a fixed markup (see Markup% computation basis) the selling prices can follow.

Affects: Product, Purchase Inbound

Auto-print after Save?​

Choices: Yes / No

  • Yes: right after you save or approve a transaction in this module, CIRMS opens the print preview with the template chosen in the next setting. If Enable Printing of Transactions Only When Approved is on, it only prints when the transaction is approved.
  • No: nothing prints automatically; use the print button when you need it.
  • Approve and Print always prints (for users allowed to approve and print), whatever this setting says.

Auto-print only works for users with the module's print permission, and each auto-print counts toward the print preview limit set in Transaction Preferences.

Affects: Purchase Inbound

Set the default printout template for this transaction module​

Choices: Choose from a list

The printout template used by auto-print and by Approve and Print in this module. The list shows the templates made in Printout Template for this module.

Affects: Purchase Inbound

Show warning if have same serial number from old purchase return detected. This is to prevent receiving of repaired or refurbished stocks.​

Choices: Yes / No

  • Yes: when you save a purchase inbound with serial numbers, CIRMS checks whether any of them were returned to a supplier before and warns you, so repaired or refurbished units aren't received as new.
  • No: no check.

Affects: Purchase Inbound

Import from Data Collector: Use price based on Web System's Purchase Price — Follows purchase and other payment price based on setting.​

Choices: Yes / No, follow price from Data Collector / Ask every time during importing

When you import a data collector transaction into a purchase inbound:

  • Yes: prices are replaced with the web system's purchase prices (as set in Price Based on).
  • No, follow price from Data Collector: the prices from the data collector are kept.
  • Ask every time during importing: CIRMS asks during each import (users without the permission to alter prices get the default).

Affects: Purchase Inbound

Apply counter checking of serial number or batch by re-scanning it to another modal window? — Transaction will not proceed if serials or batch are not fully validated. Auto assign batch name will not work once this feature is enabled​

Choices: Yes / No

  • Yes: after entering serial numbers or batches, users must scan them again in a separate check window. The transaction can't be saved until every serial/batch is confirmed, and batch names can't be generated automatically.
  • No: no second check.

Affects: Damage Outbound, Purchase Inbound, Purchase Return Outbound, Inventory Transaction Summary Report

Allow transacted and unavailable serials to be used by other products.​

Choices: Yes / No

  • Yes: a serial number that already belongs to (or was used by) one product can be used for another product.
  • No: a serial number can only belong to one product; saving is refused if another product already uses it.

Affects: Purchase Inbound

Auto input product Quantity and UOM base on History?​

Choices: No / UOM Only, base on product's Last Transaction / UOM Only, base on supplier history / UOM Only, base on product's supplier MOQ / QTY and UOM, base on product's Last Transaction / QTY and UOM - base on supplier history / QTY and UOM, base on product's supplier MOQ

When you add a product to the transaction, CIRMS can fill in the unit (and quantity) for you:

  • No: the product's default unit, quantity left for you.
  • UOM Only, base on product's Last Transaction: the unit is taken from the product's last transaction, from this supplier's history, or from the supplier's minimum order quantity (MOQ) setup.
  • QTY and UOM, base on product's Last Transaction: the same sources, but the quantity is filled in too.

You can still change the values on the row.

Affects: Product, Supplier, Purchase Inbound

Allow over-receiving from purchase order?​

Choices: Yes / No

For a purchase inbound created from a purchase order:

  • Yes: you can receive more than the quantity still remaining on the purchase order.
  • No: saving or approving is refused if a product's quantity is more than what remains.

Affects: Purchase Inbound

Auto generate product batch during inbound transaction​

Choices: No / Yes

For products managed by batch:

  • Yes: you don't have to enter batches. Any quantity without a batch gets a new batch named after the sheet number (for example PI-0001_1).
  • No: the batch quantities must add up to the row's quantity before you can save.

Affects: Purchase Inbound