How emko cloud works
Most business software is a collection of apps that agree to exchange data. emko cloud is one system where nine business areas read and write the same records. That single difference is where every other advantage comes from.
The centre: people and companies
Two record types sit at the middle of everything.
Person is a human being — one record, reused everywhere. The same person is referenced by a login, an employment record, a CRM contact, a project's manager, a team's membership, a story's assignee, a task's owner, a call's participants, a meeting's attendees, a course's author, a warehouse's contact and a stocktake's operator.
Account is an organisation you deal with — customer, supplier, vendor or competitor. The same account is the buyer on an invoice, the seller on an order, the employer behind a CRM contact, the target of an opportunity, the competitor you lost to, the named recipient of a price list and the vendor on a marketplace line.
Change a phone number once. It's correct in nine places, because there was only ever one place.
The chain: lead to cash
Lead → Opportunity → Quote → Order → Units → Invoice
- A lead is scored, staged and attached to a company.
- It becomes an opportunity with a value, a close date, deal roles and interest in specific products from your real catalogue.
- A quote prices it, with a validity window and line items drawn from a price list published to that specific buyer.
- The customer confirms and it becomes an order — buyer, seller, expected and actual delivery dates, the same line items.
- Receiving the order creates the physical units in your warehouse in the same operation. Not a second data entry job.
- The invoice is built from the confirmed order and records the exact units it covers, with net, tax and gross totals.
If you lose the deal instead, you record why, and against which competitor — which is itself an account you can report on.
Module by module
CORE — the shared spine
People, companies, logins, teams, projects, project teams, and a built-in CMS of nestable Markdown pages with real paths and draft/publish.
Teams and projects aren't tags. They're permission scopes: grant someone access to a project and the whole system understands what that means.
OMS — Orders
Price books, price lists, quotes, orders, invoices, rentals, reservations.
- Price books hold multiple currencies at once, published to named customers only.
- Invoices arriving by email or payment gateway land as claimable records to accept or reject — not attachments in someone's inbox.
- Rentals run a real lifecycle: reserve, start, return, complete, with an actual return date and an invoice on completion.
- Money is a first-class value with a currency, never a float.
WMS — Warehouse
Inventory that counts items, not quantities.
- Every physical unit is its own record with its own history: arrival, reservation, sale, write-off.
- Warehouses nest — sites, rooms, shelves, all the same thing.
- Expiry dates on units make first-expired-first-out a query, not a policy document.
- Stocktakes compare expected against scanned and hand you the discrepancies.
- Damaged and lost stock is written off with a reason and an amount, never silently deleted.
PIM — Products
One catalogue, every channel.
- Products and variants are modelled separately, so colour, size and material don't multiply your product list.
- Barcode, UPC, GTIN, ISBN and marketplace identifiers on one shared field.
- Media galleries with alt text and display order, at product and variant level.
- Attributes and dimensions are open key/value, because the shape varies by product type and that's allowed.
MP — Marketplace
A B2B marketplace, not a shopping cart.
- Multi-vendor by construction: every line knows which company is selling.
- Prices come from your contract price lists, with quantity tiers and validity windows.
- Carts convert to quotes, with the originating price list recorded on every line.
- Lines snapshot name, vendor and price at the moment of adding, so a later price change never rewrites history.
- Publishing is approval-gated, with a batch path for bulk loads.
CRM — Sales
A pipeline that ends in an invoice, not a closed-won label.
- Calls, emails, meetings and tasks attach to the lead and the opportunity.
- Contacts model a relationship with dates, not a duplicated person record — people change employers.
- Lifecycle stages, deal roles, lead scoring, and structured loss reasons naming the competing account.
APM — Projects
Project work that shares a spine with the rest of the business.
- Stories and tasks live under the same project your rentals, positions and costs do.
- Refinement readiness is tracked separately from status, so "ready" means something.
- A sales follow-up and an engineering task are the same kind of task. Nothing is lost at the handoff.
- Team backlogs with an explicit product owner.
LMS — Learning
Training built as a map, not a playlist.
- Courses are graphs: pages placed on a canvas, connected by weighted, typed edges.
- Course content is the same CMS your team already writes in.
- Learners flag exactly where they got stuck, and you get a ranked list of your material's weak points.
- Publish a course publicly or keep it inside the company.
ATS — Hiring
Hiring that starts from the project plan.
- An unfilled position on a project becomes a job posting with one action.
- Positions are copyable: open five identical seats without filling in five forms.
- Candidates are scored against a rubric with gates and weighted dimensions, so a decision has a paper trail.
Everything, everywhere
Three things work identically across all nine modules:
- Notes. Attach a comment to any record in any module. One commenting system, not nine.
- Tags. One vocabulary shared across stories, tasks and products.
- People. Employment is a record about a person with a start and an end, so leavers don't vanish from your history.