order → shortage → vendor POChecking the BOM by hand
Multiplying quantities across a spreadsheet, then comparing to a stock report that may be days old.
Working out who to ask
Splitting the shortage list by vendor, and finding the last price each one quoted.
Typing the PO
Copying lines into a Word or Excel template, saving a PDF, writing the email, remembering to cc the buyer.
Chasing delivery
No single place that says which POs are late, which were confirmed, and what has arrived.
Enter the customer order
Pick the product, the quantity, and the date the order must be ready to assemble. Procure works backwards from that date.
- Order number and customer reference
- Needed-by date drives every order-by date
Explode the bill of materials
Procure multiplies the product's BOM by the order quantity, and lists each part you must have.
- Quantities per unit come from your BOM
- Part codes and descriptions match your master
Subtract stock to find the shortage
Only what you don't already hold goes on a PO. If a part's stock hasn't been refreshed for two days, Procure flags it so you don't order against a stale number.
- Stock comes from Tally or an import
- Short parts are highlighted on the order
Draft one PO per vendor
Shortages are grouped by each part's preferred vendor, priced from your price list, with GST and the vendor's payment terms. Parts with no vendor are listed under "Needs a decision" instead of being dropped.
- Order-by date = needed-by date minus the vendor's lead time
- Drafts are editable until approved
Approve, and the email goes out
A purchaser or owner approves. The PO is queued, built as a PDF, and emailed to the vendor with automatic retries. The sender reads "Your company via Procure", replies go to your address, and the buyer is copied.
- Viewers can read but cannot approve
- If a send fails it retries, then tells you
Track it to received
Each PO moves through sent, confirmed, shipped, and received. Late ones rise to the top of Today. When every PO is received, the order is ready to assemble.
- Every change is written to an audit trail
- Cancelling a PO needs a reason
Order-by dates, not due dates.
Each entry is the day the PO must go out for parts to arrive in time.
Late is impossible to miss.
Overdue POs are marked and counted in the page header.
Decisions are separate.
Parts with no vendor and parts with stale stock sit in their own list.
Orders
Customer orders with required-by dates, shortage view, and a progress bar of parts received.
Parts and BOM
Part master and a bill of materials for each product. Long Tally part names are shortened safely and stay matched.
Stock
Stock levels from Tally or import, with a flag when a part's stock is older than two days.
Vendors and prices
Vendor master with terms and lead times, plus a price list per part and vendor used to price every PO line.
Purchase orders
Draft, approve, send, confirm, ship, receive, or cancel. One PO per vendor per order, with GST lines and totals.
PO email and PDF
PDF built for each PO and sent by a background worker with retries. Each send is logged against the PO.
Today and order-by
The dated view, late counts, orders in progress, and a list of decisions waiting on you.
Import
Bring parts, BOMs, vendors, prices, and stock in from CSV files. Files are checked first; if any row is wrong nothing is imported.
Tally agent
A small program on the client's PC reads parts, stock, and creditors from Tally and sends them to Procure.
Audit trail
Who approved, sent, cancelled, or changed what, and when. Entries cannot be edited or deleted.
Users and roles
Owner, purchaser, and viewer. Only owners change settings or remove vendor data.
Settings and privacy
Company details for the PO, email retention period, and anonymise or delete a vendor's personal data on request.
The agent reads parts, stock, and creditor ledgers, including creditors held in sub-groups.
Export a spreadsheet and import it as CSV. Same parts, stock, and vendor data, brought in by file.
The agent only reads from Tally and talks to Procure over HTTPS.
Each client is separate
Every record belongs to one client. Queries that forget to name the client fail instead of returning someone else's data.
Support access is visible
Our staff see a client's data only while an access grant with a written reason is open. Clients see every grant in Settings, and each request is logged.
History you can rely on
The audit trail is append-only, enforced in the application and by database triggers on PostgreSQL.
Sign-in is throttled
Repeated failed logins from one address are slowed down, and actions on the site are POST-only with CSRF protection.
Vendor privacy
Anonymise or delete a vendor's personal data when asked, and choose how long email logs are kept.
Email that lands
POs are sent from the platform's own address with your name on it, so vendors' spam filters don't see your domain being spoofed.
Trial
No card needed
One real order, your own BOM and stock file.
- All modules
- 1 user
- Import from CSV
- Email support
Team
Save 17%: two months free
A purchaser and a few approvers in one company.
- All modules
- Up to 3 users
- Tally agent or CSV import
- Email support
Business
Save 17%: two months free
Purchasing, stores and management, all signed in.
- All modules
- Up to 10 users
- Tally agent or CSV import
- Priority support
Custom
Priced on users and companies
More users, several companies, or a rollout plan.
- All modules
- More than 10 users
- Several companies
- Guided onboarding
Prices in INR, excluding GST. Onboarding, Tally agent setup, and the first data import are quoted once per client. These are working numbers for discussion, not a published price list.
No. Procure keeps no accounts. With Tally, a small agent on the client's PC reads parts, stock, and creditors. With Busy or anything else, export a spreadsheet and import it as CSV.
Run your next order through Procure.
Bring one real customer order, its BOM, and your stock file. We'll show you the vendor POs it would have drafted.
Procure is built and run by Code5X. See our other work on Projects.