All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Media ERP
  2. Features
  3. Customer orders
Feature · Customer orders

Customer orders

A sales representative prepares the offer against a named customer, entity, selling unit and current price basis. The accepted order carries quantity, net value, ship-to details and the title rule into fulfillment.

OverviewOrders Awaiting Approval
Media ERP · Customer orders

Orders Awaiting Approval

Approval conditions

New
Order numberAdvertiserOrder dateNet totalCredit reviewSnapshot
AO-78234ADV-896205 Oct280CR-79374DR-65825
AO-87758ADV-634514 Oct320CR-73539DR-19648
AO-31395ADV-103210 Oct700CR-85638DR-40716
AO-38911ADV-836708 Oct650CR-55416DR-25839
AO-87077ADV-547412 Oct590CR-17773DR-66522
6 of 6 records
ADV-8962Ad orders · AO-78234
Submitted
Order date05 Oct
Net total280
Credit reviewCR-79374
SnapshotDR-65825
Example screen with sample data

What you can do

Customer orders in daily work

A sales representative prepares the offer against a named customer, entity, selling unit and current price basis. The accepted order carries quantity, net value, ship-to details and the title rule into fulfillment. The team keeps each handoff tied to its source record so changes to a later step do not quietly rewrite the earlier decision.

A sales representative quotes a stocked item to a customer with agreed terms. The representative records the quoted quantity, expiry and acceptance evidence. The sales manager reviews the accepted order revision; finance handles a credit exception when the proposed exposure exceeds the customer limit. Keep the approved revision with the work. When circumstances change, record the correction or next decision against that version.

How the work is organized

  • Quote. Sales Representative records the item, selling unit, price and expiry before sending an offer.
  • Accept. Sales Manager reviews the current order revision; Finance Manager decides a credit exception when required.
  • Fulfill. Warehouse Operator works from accepted line quantities, leaving the unshipped remainder visible.

The preparation and execution records answer different questions. A planned quantity describes intent; a posted movement, accepted receipt or confirmed payment describes what actually occurred. Keep both when comparing what was promised with what happened.

What to agree during setup

Agree who maintains the customer billing identity, who may alter pricing, and which evidence proves customer acceptance. Set a finite credit limit and decide when dispatch or delivery transfers title. Document the decision owner for each exception. Give users only the entity and location scope they need. Use a pilot with an ordinary case and a partial or failed case before allowing routine work to depend on the configuration.

The item code and customer or supplier identity should stay stable during migration. Where a document carries a currency or unit conversion, retain the applicable version with that document. A later master change should apply to future work, not change an accepted transaction.

Check the handoff on an actual case

Follow one accepted order through a partial shipment. Compare accepted line quantity with each fulfillment and billing allocation. A second attempt to claim the same quantity must be held for review. Ask the preparer and decision maker to review the same case separately. Compare the source quantity, the actual recorded quantity and what remains available for the next step.

The receiving team should be able to explain why the record is ready, what still needs review and who owns the exception. Rehearse a repeat submission and a changed source after approval. Keep the original evidence visible when the case is corrected.

What your team sees

  • Customer Order Board — See draft, submitted and accepted orders with their owners and remaining work.
  • Orders Awaiting Approval — Review submitted orders before stock is committed.

Follow the work through

What it keeps track of

Data model
Advertisers
Entity-scoped trade customers, including dealer terms, holds and billing identity.
Advertiser contacts
Contacts and delivery sites belong to the dealer and are separate from authentication.
Quotes
Versioned dealer offers with known pricing basis and real acceptance lineage.
Quote lines
All line/header discounts allocated once into accepted net value.
Ad orders
Dealer-accepted scope plus mandatory independent commercial approval.
Ad order lines
Bounded accepted quantity/value and retained original promise.
Credit reviews
Atomic dealer exposure review and separately bounded exception.
Rate cards
Effective entity/currency dealer pricing; no accepted-price mutation.
Rate card entries
Quantity-tier price basis in a named product unit.
Approval decisions
Authoritative human decisions independent of document lifecycle.

Who uses it

Permissions
Sales Representative
, Sales Manager and Finance Manager.
Each person acts within their assigned entity and work scope.

Set up Media ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started