Registering Order Types

In Demander Web it is possible to register, edit and also delete Order Types.

Registering Order Types requires some mandatory fields, such as Code and Description, and also other optional fields, such as “Payment conditions”, “Type of flex balance operation”, among others.

To do so, simply follow the path below and fill in the fields as needed.

*Mandatory fields.Data Tab*Code: Must be a unique Code per Order Type. (It is not possible to have the same codes).

*Description: Name to identify the Request Type. Examples (Sale, Bonus, Exchange).

*Active: Inactive Order Types do not appear when issuing the order.

Configuration tabOrder type for stock by order type:

Defines for which type of order the Stock by Order Type x Seller, also known as Ready-to-Deliver Stock, will be used. In addition to setting this option, some configuration is required. In the Company Settings “Additional Settings” tab, the “Inventory Control” option must be set to “Validate stock by order type x seller”. It is also necessary to have ready-to-deliver stock registered, see our article Registering Ready-to-Deliver Stock.

Flex balance operation type:

Defines the behavior of the Flex Balance for the Order Type. Standard Behavior: The calculation is made based on the order item, if there is a discount, debit it from the flex, if there is an increase, it adds it to the flex. Total credit in the Order: Adds the positive flex value to the total order. Debit total on Order: Decreases the negative flex value on the order total. Do not determine Flex: Flex is not determined for this Type of Order. Required settings: In the Company Settings tab “Additional settings” the configuration:
- “Make the Flex Balance button visible on Demander mobile” must be “Visible”. “Enable monthly flex balance control” has two options: * “Yes”, The Flex Balance is controlled by Demander. A value is entered in the seller’s registration that he can use to give a discount, when it reaches zero he can no longer use it. At the beginning of next month this value will become available again. * “No”, The Flex Balance is controlled by the ERP. (If the ERP has the Flex Balance concept). Debits and Credits are sent to the ERP, which after processing returns the Flex information to the Demander. “Flex Balance calculation type”, must be configured according to the Company’s needs, there are two types. *Default: The calculation is made based on the order item, the increase credits flex, the discount debits flex. *Flex Range by Price List: On the https://sistema.demander.com.br/dinamico/faixa-flex screen, it is possible to configure a flex range based on a price list, and define when the flex will start to take effect. They can have several flex ranges. For more details see our documentation on Flex Balance

*Inventory Control Behavior (Required) This field defines how inventory control will be managed, depending on the type of order.

Product Stock: It will be validated by the product stock as defined in the product.
Stock by Branch: Validation will be done based on the stock available in each branch.
Ready Delivery Stock: Stock will be validated based on the availability of items for immediate delivery.
According to Company Configuration: Stock will be validated as configured in the company.

Status that allows editing:

Defines which Status the Order must have to be able to be edited after synchronization. If no status is selected, it is possible to edit ALL orders that appear for the seller. For this configuration to work, the setting “Allow editing after synchronized order” must be checked.

Released Price Lists:

Only price lists configured in this field can be used with this type of order. If no list is configured, all price lists can be used in the order.

Consider as requested:

Defines whether this Order Type will be considered as an Order.Attention: This configuration affects several validations in Demander, see for which validations this option must be selected. Flex Balance Calculation: The Flex Balance is only calculated on Order Types that “Consider as Order”. Last price suggestion: Only the last price is suggested in Order Types that “Consider as Order”. Commission calculation: Commission is only calculated on Order Types that “Consider as Order”. Goals (Sales Expectation): Goals are only calculated on Order Types that “Consider as Order”. Do not forget product: Product is only suggested in the Order in Order Types that “Consider as Order”. Stock balance validation: Product stock is only validated in Order Types that “Consider as Order”.

Consider latest sales

Enabled: The type of order will be considered in the latest sales histories. Disabled: This type of order will not be considered in the latest sales. Attention: Only the type of order that has this check box marked in the “Configuration” tab of the Order Type will be considered.

Requires link with order:

Defines whether the order must be linked to another order, but only considers orders issued in the last two days. Example of use: Company has 2 types of order, 1 – Sale which does not require link with order and 2 – Bonus which requires link with order. Let’s say the seller placed an order with type 1 – Sale and then placed another order for the same customer with type 2 – Bonus, before starting to enter the second order, he will be asked which order the bonus will be linked to.

Allows editing after synchronized order:

Defines whether the order can be edited after synchronization. By default, this option is disabled and the seller can only edit orders that he has not yet synchronized. By enabling this setting, the seller can also edit orders that have already been synchronized. In the field “Status that allows editing” you can define one or more statuses that allow editing. By leaving the field blank, all Order Types can be edited after synchronization.

Validate stock balance:

By enabling this option, orders of this type will now validate the stock balance of the products.

For validation to work correctly, it is necessary that, in the company settings, in:

Company Settings → Order → “What behavior should the system have in relation to the stock balance of products?”,

the option “Prevent sale if balance is insufficient” is selected.

Discount balance in calculated stock:

When enabling this option, orders of this type are now taken into account when calculating the available stock balance.

Requires issuance of NF-e: When registering new orders, the issuance of NF-e will be mandatory.

Send upon return to ERP: It is used when the ERP does not have numbering control, so to prevent the ERP from inserting the same order more than once, this option must be unchecked.

Considers credit limit: Allows you to use the credit limit as a payment condition, if it is used, customers will not be allowed to place orders that exceed the value of the imposed limit.

Requires registration update: Defines whether this type of order will require registration updating. (NOTE: This configuration only takes effect if the company uses the Registration Update module.)

Requires Purchase Order (according to customer): Defines whether this type of order will require the purchase order field to be completed according to the selected customer. If this setting is checked, even if the customer “requires purchase order” it will not be mandatory, this is useful for some types of orders such as Exchange and Bonus.

Ignore Discount Validation: If checked, no discount validation will be carried out on the order or on the order items.

Minimum quantity of units: This setting defines the minimum quantity of units required in an order. Prevents an order from being placed if the number of units is lower than the configured value.Behavior in relation to the sale of broken packaging: Broken packaging is used when the company has defined that it sells the product in closed packaging. This configuration defines the behavior in case of breakage of this packaging. Example: My company sells a product with a package of 12 units, but the customer wants to buy 6, what behavior will the Demander have if the seller places 6 units in the application? There are 3 configuration options: “Do not perform this validation”, in this case the Demander does nothing, the seller can sell the 6 units without problems, “Prevent the sale”, in this case the Demander does not allow the seller to place an order with a quantity other than multiples of 12, that is, it allows placing an order with 12, 24, 36, 48… units, but does not allow selling with 6 units. “Alert the seller, but do not prevent the sale”, in this case the Demander shows a notification that the packaging has broken, but does not prevent the sale, the seller can sell the 6 items normally.

Blocked for payment terms: Defines for which payment terms the order type cannot be used.

Which taxes should be calculated: Defines which taxes should be calculated on the order type. (Ex: IPI, ICMS ST, Additional Rate).

Release hierarchy behavior: Defines the Release Hierarchy Behavior that will be used in the Order Type.

Does not require release: No type of release will be required by the seller.
Always Requires Release: All orders placed with this type of order will have to be released by a salesperson or manager as defined by the company, before being invoiced.
Only when Extrapolating the Average Contribution Margin of the Order: Release of the order will only be required if it exceeds the average contribution margin of the order defined by the company.
When Extrapolating the Maximum Discount or Average Contribution Margin of the Order: Order release will only be required if the order exceeds the maximum discount or the average contribution margin of the order defined by the company.

Minimum Delivery Time: This field allows you to configure the minimum number of delivery days after the current date. (Ex: If it is set to “1”, it means that the minimum expected delivery would be tomorrow.)

Maximum Delivery Time: This field allows you to configure the maximum number of delivery days after the current date. (Ex: If it is set to “5”, it means that the maximum delivery forecast would be today plus 5 days.)

Default delivery time (business days): When defined, the system automatically suggests the delivery time when issuing orders. (Formula: Today + number of business days configured.)

Contribution Margin Behavior:

Do not validate: Will not display or validate the contribution margin. (This option is the Demander default setting.)
Display contribution margin and validate: Will display and validate the configured contribution margin.
Only validate the contribution margin: It will validate the configured contribution margin, but it will not be displayed.
Display the contribution margin but not validate: It will display the contribution margin but will not be validated.

% Variable Cost: Determines the percentage of variable cost considered in calculating the Contribution Margin.

Status of Orders saved but not released to the ERP: Determines the status that orders saved, but not released, should assume. Important: Configure a status here that does not send these requests to the ERP, unless you want to monitor them in real time. Status of orders released to the ERP: Determines the status that orders recently released by the seller must assume.Important: Ensure that the order status configured here releases the order to the ERP (unless you use the Order Picking module.) Order Type Color (hexadecimal): The Status Color field allows you to customize the status color in a visually appealing way. Here you can define a hexadecimal color in the format #ffffff. This color will be used in some places on Demander to identify status.Date Inserted: Displays aData/Time the record was created.

Date Changed: Displays aData/Time of last record change.

Consider recent sales