iVendNextDevelopers Request a sandbox

Item Price

One item's price in one price list, in one unit.

Area: Prices and price lists · Why it is here: guide chapter 01c; guide chapter 07; recipe approvals; recipe approvals_stores; recipe derived_price_lists; recipe estate_rollout; recipe expiry_markdown; recipe print_pack; recipe system_sync; sample S11; sample S14; sample S23; sample S26; retail core · Fields: 19

iVendNext's own description: Log the selling and buying rate of an Item

Read and write it

Every call runs as your app's own user, with its key in one header, at the retailer's own address. The user reads and writes only what its role allows: your app's user, and the rights the retailer gives it.

Read a list (only name unless you ask for fields):

curl -s "https://⟨site⟩/api/resource/Item%20Price?fields=%5B%22*%22%5D&limit_page_length=20" \
  -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Read one:

curl -s "https://⟨site⟩/api/resource/Item%20Price/⟨name⟩" -H "Authorization: token ⟨api key⟩:⟨api secret⟩"

Create one (the required fields first), if your app's role may:

curl -s -X POST "https://⟨site⟩/api/resource/Item%20Price" -H "Authorization: token ⟨api key⟩:⟨api secret⟩" \
  -H "Content-Type: application/json" -d '{"item_code": …, "uom": …, "price_list": …, "price_list_rate": …}'

Change one with PUT /api/resource/Item%20Price/⟨name⟩ and the fields you change; a table sent there replaces its rows, so send its existing rows too. All the record calls and their answers: the API reference.

Samples that use it

s5_config_pack · s7_system_sync · s8_estate_rollout · s10_ai_manager · s11_approvals · s14_approvals_stores · s23_till_guard · s26_derived_prices · s29_print_pack · s30_units_as_serials · s38_expiry_markdown · s43_third_party_payer · s52_phone_plans

Fields

Read from the product at POS 2.1.0.667 (till app 60147699c): its own fields, the fields iVendNext adds to it, and iVendNext's changes to any of them. Read-only fields are set by iVendNext; a hidden one is not on the form but can be read. Every record also has name (its id, in the address), owner, creation, modified, modified_by and docstatus (0 a draft, 1 submitted, 2 cancelled), all read-only.

Field Field name Type Required Read-only Hidden Links to
Item Code item_code Link yes Item
UOM uom Link yes UOM
Packing Unit packing_unit Int
Item Name item_name Data yes
Brand brand Link yes Brand
Item Description item_description Text yes
Price List price_list Link yes Price List
Customer customer Link Customer
Supplier supplier Link Supplier
Batch No batch_no Link Batch
Buying buying Check yes
Selling selling Check yes
Currency currency Link yes Currency
Rate price_list_rate Currency yes
Valid From valid_from Date
Lead Time in days lead_time_days Int
Valid Upto valid_upto Date
Note note Text
Reference reference Data

All record types · What you can use

This record type in the kit