View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Retail:SupportForAttributes

Contents

Introduction

This document holds the configuration required for performing a Sales or Return transaction using an instantiable attribute of the product in Openbravo WebPOS.

Bulbgraph.png   This feature is available starting from RR17Q4

Objective

Some products are identified in stock by instantiable attributes like serial number, lot number, expiration date and others. Any material movement of those products require the attribute information to be provided, so the stock is always informed about the specific attributes available. It allows better traceability and control.

Openbravo supports products identified by attributes. But current Openbravo Web POS does not allow to read attribute information when selling or returning, so the system decides (as per FIFO or other rules) which specific items (with specific attribute values) are shipped for any sale from Web POS.

The objective of this new feature is to allow reading attribute information from products sold and returned in Web POS, so this info is used for actual shipping based on the attribute values read from the items sold.


Configuration

1. Enable Preference: To be able to use this functionality a preference should be enabled. Go to Preference and search the Property = "Web POS Enable support for product attributes" and change the Value = Y.

OBSFA Preference.png

2. Re-Login into Openbravo WebPOS to load new preference changes.

Usage

Sales Flow

When a product is selected (scanned or browsed) having an instantiable attribute, a popup will appear to input the attribute set value.

OBSFA AttributePopup New.png

The value of an attribute should be syntactically correct. For example, if the attribute is defined as follows:

Example 1:
Attribute Name: Purchase Lot
Lot: Y
Serial No. : Y
Expiration Date: Y
Then a valid attribute set value can be: LSEP06_#6969_15-10-2018

Example 2:
Attribute Name: Purchase Serial No
Serial No. : Y
Expiration Date: Y
Then a valid attribute set value can be: #6969_15-10-2018

Once the attribute set value is scanned, the entered attribute set value is displayed in the ticket lines. While synchronizing the order if the attribute set value entered by the user is not available in the back office, the attribute set is created and associated with Sales Order and Goods Shipment.

Stock Validation

If the Enable Stock Validation preference is enabled, the validation of the stock will be done using the attribute set value entered by the user.

OBSFA StockValidation.png

Return Flow

When a Verified Return transaction is created, the attribute set value is loaded from the Sales Order if it was used while creating an order. A popup is raised for the user to scan the attribute set value which will be validated against the Sales Order.

OBSFA VerifiedReturnPopup.png

Once the attribute set value is entered a visual feedback is provided to the user by changing the background color of the text field. Green or Red signifying if the value entered matches with the Sales Order or not. Until all the values entered are correct the user cannot proceed with the flow.

OBSFA ValidateVerifiedReturnPopup.png


When a blind return is performed, the attribute set value entered by the user is created in the back office while synchronization of the blind return order.

Quotation

When converting a Quotation to Sales Order, the user should provide the attribute set value for the product.

To use this feature you need to enable a preference named Web POS Ask for attributes when Quotation to the Sales Order.

Once the preference is enabled, you will be asked to enter the attribute value for the product while converting the Quotation to the Sales Order.


OBSFA QuotationToSalesOrder.png

Retrieved from "http://wiki.openbravo.com/wiki/Retail:SupportForAttributes"

This page has been accessed 475 times. This page was last modified on 19 June 2017, at 08:38. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.