What this page is
In plain English
This page is not a contract and you are not agreeing to anything by reading it. A Krepko pilot is agreed in a Service Order that both sides sign. This explains what that document covers, so nothing about the commercial arrangement is a surprise by the time you get to it.
A summary for orientation. The wording below is what applies.
This page describes the framework within which a Krepko pilot is agreed. It is not an offer, it is not capable of acceptance, and it creates no obligation on either party. The binding terms of any pilot are those recorded in the Service Order executed by the customer and Krepko Pty Ltd, together with any terms that document incorporates. Where anything on this page differs from a signed Service Order, the Service Order prevails.
Services and modules
In plain English
KSuite is the commercial package that shows the modules working together; it is not itself where the work is recorded. Each module owns its own area, and only the functions named in your Service Order are switched on.
| Module | Owns |
|---|---|
| Kat | Calls, requests, consent and identity steps, context, ticketing, summaries, assignment and follow-up. |
| KSafe | Inventory, invoices, receipts, batches, shelves, stocktakes and discrepancies. |
| KDash | The unified operational surface and attention layer. It reads and coordinates; it does not replace the other modules. |
| KMail | Audiences, exclusions, governed templates, approval, scheduling, automation, dispatch, delivery outcomes, feedback and promotional coupons. |
| KShop | Customer access and the complete order workflow. |
A summary for orientation. The wording below is what applies.
KSuite is the connected commercial package that shows cross-module handoffs; it is not an operational endpoint or source of truth. Kat owns calls, requests, consent/identity steps, context, ticketing, summaries, assignment and follow-up. KSafe owns inventory, invoices, receipts, batches, shelves, stocktakes and discrepancies. KDash is the unified operational surface and attention layer; it reads and coordinates but does not compete with module sources of truth. KMail owns audiences, exclusions, governed templates, approval, scheduling, automation, dispatch, delivery outcomes, feedback and promotional coupons, and uses Inbox as its communications execution layer. KShop owns customer access and the complete order workflow. Exact enabled functions are only those listed in the Service Order.
Pilot and Service Order
In plain English
A pilot is open to any community pharmacy in Australia, and there are 15 places. It runs for twelve weeks unless you agree something different with us, which is long enough to cover a full dispensing cycle and at least one month end. It can cover every module or only the ones you want to try. What is included, when it runs, who takes part and what it costs are written into a signed Service Order before anything begins. No amount is published here, and agreeing to a pilot does not commit either side to anything beyond it.
A summary for orientation. The wording below is what applies.
The Pioneers pilot is open to any community pharmacy operating in Australia, and may evaluate all modules or a selected subset. The Pioneers group is limited to 15 pharmacy partners.
The standard pilot term is twelve weeks from the commencement date recorded in the Service Order, so that the evaluation spans a complete dispensing cycle and at least one month end. A different term applies only where the Service Order records it.
Scope, functions, integrations, dates, participants, acceptance activities and charges are recorded in a signed Service Order. Any pilot charge is a tailored discounted quote based on that agreed scope; no pre-set monetary amount is published here and no obligation arises to proceed beyond the pilot.
How a pilot is agreed and invoiced
In plain English
Four steps, and nothing is agreed until the third one. You are not committed by talking to us, and no charge arises before the Service Order is signed.
| Step | What happens |
|---|---|
| Introductory call | We work out what your pharmacy actually needs and whether a pilot is worth either side’s time. |
| Written scope | We put the modules, functions, integrations, dates and participants in writing for you to check and correct. |
| Service Order | The agreed scope becomes a Service Order. Signing it is the point at which anything is agreed. |
| Onboarding | Access, configuration and the agreed testing begin. |
A summary for orientation. The wording below is what applies.
A pilot is agreed in four stages: an introductory discussion; a written scope prepared by Krepko and confirmed by the customer; a Service Order executed by both parties; and onboarding. Nothing is agreed and no charge arises before that Service Order is executed. Anything said or written during the first two stages is indicative only, and is superseded by the executed Service Order.
Charges quoted in a Service Order are exclusive of goods and services tax, which is applied at the rate applicable at the time of supply. Krepko invoices monthly in arrears for the period just completed, and each invoice is payable within fourteen days of the date of issue. Any other arrangement, including any deposit, milestone or advance payment, applies only where the Service Order says so.
Dependencies and integrations
Delivery may depend on customer systems, third-party providers, credentials, data quality, connectivity and approvals identified in the Service Order. An integration is included only when named there. The effect of delay, third-party change or unavailable access is allocated in that order rather than assumed here.
Customer responsibilities
The customer nominates authorised contacts, provides lawful and accurate inputs, controls user access, completes agreed testing and decisions, and continues professional and pharmacy oversight. The customer must not provide data outside the agreed pilot scope. A pharmacy remains responsible for its own professional and clinical decisions; no Krepko module makes a dispensing decision.
Data handling
The Service Order identifies the permitted data, roles, access, environments, retention, deletion and export steps, and any separate data-processing terms that apply between the parties. How Krepko handles personal information across its services, including where that information is processed and stored, is described in the Krepko privacy policy.
Support and changes
In plain English
You get a named person at Krepko and an email address that reaches them, during Australian business hours. We do not publish a response time, because a promise we cannot always keep is worth less than no promise at all. If you want the pilot changed, both sides sign a short written variation before it happens.
A summary for orientation. The wording below is what applies.
Each pilot is assigned a named Krepko contact, reachable by email and during Australian eastern business hours on business days in Queensland. Krepko publishes no response time, no availability target and no service credit, and none is created by this page. Where a Service Order records a specific support commitment, that commitment applies to that pilot.
A change to the scope, functions, integrations, participants, dates or charges of a pilot takes effect only when both parties sign a written variation to the Service Order. Krepko will not enable a function, widen a data scope or begin a chargeable activity on the basis of an informal request. Maintenance notices and the pilot acceptance process are set for each Service Order.
Suspension
Grounds, notice, urgent protective action, access during suspension and restoration steps are set by the signed agreement. Any such term has to balance patient safety, lawful operation, payment and security without creating a unilateral right that has not been agreed.
Solicitor decision required: draft the suspension grounds, notice periods and restoration steps.
Termination and exit
Term, termination rights, notice, accrued charges, transition assistance, continued access, export format and deletion timing are set by the signed agreement and the applicable Service Order. Completing a pilot does not by itself authorise ongoing production service.
Solicitor decision required: draft the termination rights, exit assistance obligations and post-termination data handling.
Intellectual property and confidentiality
Each party’s existing materials remain its own, and nothing on this page transfers any right. Ownership and licensing of configuration, feedback, deliverables and improvements, and the scope, exclusions, permitted disclosure and survival of confidentiality obligations, are set by the signed agreement.
Solicitor decision required: draft the intellectual property allocation and the confidentiality regime.
Warranties and consumer law
Nothing in a Krepko agreement excludes, restricts or modifies a consumer guarantee, right or remedy that cannot lawfully be excluded under the Australian Consumer Law or another applicable law. Any express warranty Krepko gives, and any disclaimer of a warranty that may lawfully be disclaimed, is stated in the signed agreement rather than here.
Solicitor decision required: draft the permitted warranties and disclaimers and confirm the Australian Consumer Law treatment for a business customer of this kind.
Liability
No liability position is proposed on this page. Where liability cannot lawfully be excluded, a Krepko agreement does not attempt to exclude it.
Solicitor decision required: draft the liability cap, exclusions, heads of loss, aggregation and carve-outs. The commercial risk position a cap has to be set against is recorded in the review brief.
Indemnities
No indemnity is proposed or given on this page.
Solicitor decision required: decide whether any indemnity is appropriate for a pilot of this size and draft its scope, process, control and exclusions. The operational risks Krepko has identified as needing allocation are recorded in the review brief.
Disputes and governing law
A Krepko agreement is governed by the laws of Queensland, Australia and applicable Commonwealth laws. Subject to any non-excludable right to commence proceedings elsewhere, the courts of Queensland and the courts entitled to hear appeals from them have jurisdiction.
A matter that cannot be settled between the working contacts is escalated on Krepko’s side to a director who was not involved in the decision in dispute, and on the customer’s side to the decision-maker it nominates in the Service Order.
Solicitor decision required: draft the escalation and dispute procedure that precedes proceedings.
Notices, entity and execution
The contracting entity is Krepko Pty Ltd (ACN 693 126 171, ABN 20 693 126 171) of 17 Ullapool St, Heathwood QLD 4110, Australia. Notices and enquiries about a pilot or a Service Order go to team@krepko.com.au or 0434 955 303.
A Service Order may be executed on Krepko’s behalf by any director of Krepko Pty Ltd. The customer nominates its own authorised signatory in the Service Order.
Solicitor decision required: approve the notice methods, deemed receipt, counterparts and electronic execution provisions.
General terms
Assignment, subcontracting, force majeure, waiver, severability, order of priority, variation and entire-agreement provisions are set by the signed agreement. None is created by this page.
Solicitor decision required: draft the general terms, including the priority order between the agreement, a Service Order and any incorporated policy.
Decisions still open
The decisions that were Krepko’s own to make have been settled and are stated above: who is eligible, how long a pilot runs, how one is agreed and invoiced, what support it carries, who may change it, who signs it and where an escalation goes. What remains is legal drafting.
Solicitor decision required: formation, warranties, liability, indemnities, consumer-law treatment, confidentiality, intellectual property, the data-processing terms between the parties, suspension, termination, disputes, notices, execution and general terms.
Krepko has also asked for a Service Order template and a data-processing schedule to be drafted, because the framework above defers every binding term to a Service Order that does not yet exist.