Alephee developers portal
  • Introduction
    • 📘API documentation
      • Introduction to integrations
    • ⚙️Using the API
      • 🔒Authentication
      • 🏹Swagger
    • 📡Overall index of methods
  • Usage limiting
    • 🕑Rate limiting
    • 🔃Limits per request
    • ♒Limits HTTP headers responses
    • ⚠️Usage limits by endpoint
  • Accounts
    • GET methods
      • Accounts
        • ⚠️Usage limiting
        • ⬆️Request and Respone
        • ⌨️Type specifications
        • ⚙️Examples
      • Marketplaces
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • Price Lists
        • ⚠️Usage limiting
        • ⬆️Request and Responses
        • ⌨️Type specifications
        • ⚙️Examples
      • Stores
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • Login Token
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • 📊Business rules
        • Standard usage flow for Alephee B2B portal
        • ⌨️Type specifications
        • ⚙️Examples
    • PUT methods
      • Update account fiscal tax rules
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
  • Orders
    • Logical model
      • ℹ️What is an order?
      • 📂Order model overview
      • 🛒Shopping cart orders
        • 🔳Cart order model overview
        • 〽️Mercado Libre’s shopping cart orders
      • 💴Approved payments and pending payments
      • 🗒️General notes
    • GET methods
      • 👩‍💻Orders
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
        • ⁉️Useful tips
      • 🛒Orders List From A Shopping Cart
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • 📄Orders Document
        • ⚠️Usage limiting
        • ⬆️Request and Response
      • 🧾Order Shipping Label
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⚙️Examples
    • PUT methods
      • 📑Update orders status
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • 👨‍💼Mark orders as integrated
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • POST methods
      • 📑Attach document to an order
        • ⚠️Usage limiting
        • Allowed document types and formats
        • ⬆️Request and Response
        • ⚙️Examples
        • ⚙️Example using POSTMAN via form-data
        • ⚙️Example using POSTMAN via JSON body
      • 📑Split an order
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
      • 📨Send a message to a buyer
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⚙️Examples
      • 📝Create a new order
        • ⚠️Usage limiting
        • Introduction
        • 📊Business rules
        • 📑Order mandatory sections
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • DELETE methods
      • 📑Delete an order
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⚙️Examples
  • Orders shipping
    • GET methods
      • Shipping Packaging Information
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • Shipping Scheduling Information
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • Shipping Transportation Information
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • POST methods
      • Set Shipping Packaging Information
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⚙️Examples
  • Products
    • GET methods
      • Products
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • POST methods
      • Logical model
      • Business Rules
        • Prices considerations
        • Available prices attributes combinations to set prices
        • Stock considerations
        • Alephee B2B portals prices and stock considerations
        • Measurable quantity and price considerations
      • Update Products
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • PUT methods
      • Update product fiscal information
        • ⚠️Usage limiting
        • 🗒️Notes
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • DELETE methods
      • Delete products from a price list
        • ⚠️Usage limiting
        • 📊Business rules
        • ‼️Warnings
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⌨️Result type specifications
        • ⚙️Examples
        • Most common validation error messages and how to fix them.
  • Product listings
    • GET methods
      • Product Listings
        • ⚠️Usage limiting
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • POST methods
      • Set product listings discounts
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
    • PUT methods
      • Update product listings
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
      • Set product listings status
        • ⚠️Usage limiting
        • 📊Business rules
        • ⬆️Request and Response
        • ⌨️Type specifications
        • ⚙️Examples
  • GLOSSARY
    • Conventions
    • Response status codes
    • Marketplaces/Channels ID and names list
    • Product listings status list
    • Orders and shipping glossary
      • Available order statuses codes
      • State transitions diagram
      • Automatic and manual order status updates
      • Attaching documents to orders
      • Shipping labels
  • TROUBLESHOOTING
    • ❗Important tips
    • ✅Best integrations practices
Powered by GitBook
On this page

Was this helpful?

  1. Products
  2. POST methods
  3. Business Rules

Prices considerations

• All informed price fields values must NOT be empty nor 0 (zero). All values should be of as higher value than 0 (zero). Do NOT use a zero or negative price value. • All the price fields formats must be a decimal number with a period (.) as a decimal notation, no notation is needed for thousands or millions. The maximum number of decimal digits is 4. For example, 1288.44, 7430 or 7430.00. • The 'Price' (without taxes) and 'PriceWithTaxes' fields must NOT be informed at the same time. It must be one or the other. • The Cost field won’t be mandatory. • The 'SuggestedRetailPrice' field won’t be mandatory. • It will be assumed that the indicated value on the 'SuggestedRetailPrice' field already contains the proportional TAX. • The 'SalesMargin' field won’t be mandatory. Only seller type accounts may inform this value. • The 'SalesMargin' field format must be a decimal number with a period (.) as a decimal notation, no notation is needed for thousands or millions. The maximum number of decimal digits is 2. For example, 25.50, 30 or 45.00. •The “Measurable price with taxes” object is intended to replace the other price fields, using measurable price. It should only be used by those accounts that work with measurable products, such as supermarkets and other similar-type accounts. • It is mandatory to inform at least ONE of the price fields: 'Price' or 'PriceWithTaxes' or 'SuggestedRetailPrice' or 'SalesMargin' or ‘Cost’ or ‘Measurable price with taxes”. Let us brief a table with a summary of the available price attributes and when to use them:

Price attribute
Wholesaler-account type Brand-account type
Seller-account type

Price (without taxes)

PriceWithTaxes

Can use this attribute: Yes.

When: Always.

Can use this attribute: No.

When: Always.

Exceptions: Very few and rare cases depending on the wholesaler and seller relation settings.

SuggestedRetailPrice

Can use this attribute: Yes.

When: Always.

Can use this attribute: Yes.

When:

1. When the seller is disconnected from a wholesaler-type account and its product catalog.

2. When the seller is connected to a wholesaler-type account and its product catalog, but the account configuration is set to “disconnected price mode”.

Can use this attribute: No.

When:

1. When the seller is connected to a wholesaler-type account and its product catalog, and the account configuration is set to “connected price mode”.

Cost

Can use this attribute: No.

When: Never.

Can use this attribute: Yes.

When:

1. When the seller is disconnected from a wholesaler-type account and its product catalog.

2. When the seller is connected to a wholesaler-type account and its product catalog, but the account configuration is set to “disconnected price mode”.

Can use this attribute: No.

When:

1. When the seller is connected to a wholesaler-type account and its product catalog, and the account configuration is set to “connected price mode”.

SalesMargin

Can use this attribute: No.

When: Never.

Can use this attribute: Yes.

When: Always.

a) When the seller is connected to a wholesaler-type account and its product catalog, and the account configuration is set to “connected price mode”….

The sales margin will apply to the “Cost” value informed by the wholesaler.

b) When the seller is disconnected from a wholesaler-type account and its product catalog…

The sales margin will apply to the “Cost” or “SuggestedRetailPrice” value informed by the seller. Depends on the account settings.

c) When the seller is connected to a wholesaler-type account and its product catalog, but the account configuration is set to “disconnected price mode”.

The sales margin will apply to the or “Cost” or “SuggestedRetailPrice” value informed by the seller. Depends on the account settings.

Measurable price with taxes

Can use this attribute: No.

When: Never.

Can use this attribute: Yes.

When: Always.

This object is intended to replace the other price fields, using measurable price. It should only be used by those accounts that work with measurable products, such as supermarkets and other similar-type accounts.

DO NOT USE this object unless you are absolutely certain that your products use measurable quantities.

PreviousBusiness RulesNextAvailable prices attributes combinations to set prices

Last updated 2 years ago

Was this helpful?