Skip to content

Estimating for Infor CloudSuite Distribution

An emailed request for quote becomes a priced quote in your own sheet, every line mapped to CloudSuite’s product master at your markups. Your estimator reviews it, sends it and enters it as a quote in CloudSuite.

Sales & estimatingUpdated Oct 202620 ERPs

See it work on CloudSuite.

Click through the steps. Fictional data, in CloudSuite’s terms; the real thing runs on CloudSuite.

Estimating mailbox · new request
Illustrative
Dale Whitcomb, Pine Hollow ContractorsRFQ · due Oct 18

Attached material list for the detached garage at Lot 14 Birchwood. Need pricing by Friday.

Matched to Pine Hollow Contractors · 10422 · Lot 14 Birchwood garage · received Oct 15, 8:42 am

Customer, project, due date and the material list, from the estimating mailbox.

1 / 4
Request a demoSee it for Epicor Prophet 21 →See it for Epicor Eclipse →

The problem, as it happens in CloudSuite.

A request for quote is an email with a material list or a set of drawings attached. The estimator reads it, finds each item in CloudSuite’s product master, checks cost, applies the house markup for that customer, and builds the quote in the same Excel sheet the yard has used for years. Then a revision comes in.

The desk writes over a thousand quotes a year. Most of the time goes into reading and retyping, not into the pricing decisions that win the job.

How it works.

  1. 1

    The request becomes a card

    Forwarded into the estimating mailbox or opened by hand: customer matched to the customer master, project, due date, attachments. The estimator sees it on the desk with the due date on it.

  2. 2

    Lines are read and mapped

    Items read out of the material list or taken off the drawings, mapped to the product master in CloudSuite, with the matches a person should check flagged. A drawing is measured into regions the estimator confirms before anything is priced.

  3. 3

    Costed and priced

    Cost from CloudSuite, price from your versioned markup policy by customer and category. Supplier quotes you hold are priced from where you have them. The estimator sees the margin per line, not just the total.

  4. 4

    The quote, in your sheet

    The house Excel sheet and its PDF, versioned. The estimator reviews, downloads and sends from their own mailbox, and enters it as a quote in CloudSuite. Revisions are a new version, not a new file.

How it connects to CloudSuite.

Lunica reads the product master and the customer master through CloudSuite’s reporting data or APIs, under a role that can only read: current cost, the price level and markup each account carries, and the quotes already in CloudSuite’s history, so a revision is priced against what went out last time. Supplier quotes you hold are read from the share or mailbox where you keep them.

Nothing lands in CloudSuite without a person and nothing is sent on its own. The quote is written into your own sheet and PDF; the estimator sends it from their own mailbox. It goes into CloudSuite as a CloudSuite API call or import where one exists, or keyed by your team from what Lunica prepared, and Lunica records the number afterwards so the pipeline and CloudSuite agree.

What a week looks like.

  • Reading and retyping stop being the job.
  • Every quote is priced on the same policy.
  • Revisions keep their history.
  • Pipeline, hit rate and expiring quotes in one view.

Questions

Does it send the quote?

No. It tells the estimator a quote is ready. The estimator sends it from their own mailbox.

Does it write to CloudSuite?

No. Lunica reads CloudSuite and prepares the quote. A person enters it as a quote in CloudSuite, and Lunica records the number afterwards.

What about takeoffs from drawings?

Drawings are measured into regions a person confirms before anything is priced.

Will it match our sheet?

It writes your sheet, not ours. The output is the Excel file your customers already recognise, plus a PDF.

Pass-through quotes from a manufacturer?

Attached and priced from the supplier’s quote on file, with its validity date tracked.

Where does it run, and what does the model see?

On one server inside your network that connects out to Infor’s cloud, reading through CloudSuite’s reporting data or APIs, under a role that can only read. The model sees the request, its attachments and the items it is matching, not the whole product master.

Does it need a server?

Lunica runs on one server inside your network that connects out to Infor’s cloud, set up and maintained by Lunica. It reads Infor CloudSuite Distribution through CloudSuite’s reporting data or APIs, under a role that can only read. There is no inbound connection from outside your network.

What does Lunica read in CloudSuite?

The customer master, open items and terms, purchase orders and receipts, the product master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to CloudSuite?

Nothing lands in CloudSuite without a person. What belongs in CloudSuite goes back as a CloudSuite API call or import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in Infor Document Management. Lunica reads them when a workflow needs one and never writes to them.

The same workflow, on another ERP.

Estimating is written for every system on the list. You’re reading the CloudSuite version.

Wholesale distribution

Another system? Tell us which →

See it on your CloudSuite data.

Thirty minutes. We walk the workflow on CloudSuite data, then map it to yours.

Request a demoBrowse workflows