Qualification before promotion
POS reseller and implementation partner program
This page is an inquiry and due-diligence guide, not an offer of automatic acceptance. A prospective partner must verify the product, identify what it can support locally, and agree in writing who owns each customer, technical, data, payment and marketing responsibility.
An inquiry is not partner approval
A written agreement is the only partner authorization. Until it is signed, there is no approved Posnic partner title, logo use, territory, exclusivity, lead allocation, commission, margin, certification, training entitlement or support service level.
Product evidence was reviewed 18 August 2026 against stable release v1.3.0 and source commit b531ef4308c4dc3a25f250551a54fc5616e3b8d9. No complete partner-delivered customer rollout was observed.
Who should submit an inquiry
The relevant question is not a company label. It is whether the applicant can show accountable people, evidence and local operating capacity for the scope it proposes.
Implementation providers
Show experience with catalog preparation, configuration, staff training, cutover, reconciliation, backup and recovery. State the shop types and operating systems you can support.
Hardware integrators
List exact device makes, models, interfaces, drivers and service coverage. A generic printer, scanner, drawer, scale or terminal claim is not enough.
Business-system advisers
Define where product setup ends and tax, accounting, payroll, payment or legal advice begins. Name the qualified owner for every specialist decision.
Qualification path
| Stage | Applicant evidence | Required decision |
|---|---|---|
| Identify | Legal business name, registration, country, service area, languages and accountable contacts. | Which legal entities would contract and which markets are actually supportable? |
| Demonstrate | Relevant implementation work, staff skills, references used with permission and an escalation model. | Which services are evidenced and which remain outside scope? |
| Verify product | A representative Posnic pilot on the intended operating system, data, hardware, payment and backup setup. | Which workflows passed, failed or require an external dependency? |
| Map responsibility | Written ownership for customer contracting, data access, payment, tax, security, support and recovery. | Who performs, approves, monitors and retains evidence for each control? |
| Agree terms | Written commercial, brand, territory, support, incident, confidentiality, exit and dispute terms. | Is any authorization granted, and exactly what does it permit? |
| Pilot | Named customer permission, acceptance criteria, rollback plan and issue record. | Did the real customer scope pass without overstating the result? |
| Review | Support records, unresolved risks, customer feedback and current product evidence. | Should the relationship continue, change scope or end? |
Responsibility map to settle in writing
| Decision area | What the agreement must identify | Evidence to retain |
|---|---|---|
| Partner and brand status | Approved title, marks, wording, channels, countries, dates and revocation process. | Signed permission and approved current assets. |
| Customer relationship | Who quotes, contracts, invoices, refunds and owns the customer communication. | Customer contract, order and acceptance record. |
| Implementation | Data preparation, configuration, migration, training, cutover, rollback and sign-off ownership. | Scope, test results, issue log and acceptance decision. |
| Hardware | Exact models, procurement, warranty, installation, drivers, spare device and failure support. | Model inventory, test output and supplier terms. |
| Payments | Processor and terminal scope, card-data access, shared PCI duties, evidence and annual review. | Responsibility matrix, provider evidence and merchant approval. |
| Tax and accounting | Jurisdiction, configured rules, invoice fields, reconciliation and qualified approval. | Reviewed samples and named specialist sign-off. |
| Personal data and access | Controller or processor roles, permitted data, access duration, safeguards, deletion and incident notice. | Access register, agreement and deletion evidence. |
| Backup and recovery | Backup location, retention, encryption, restore owner, target times and replacement-machine procedure. | Scheduled logs and a successful restore record. |
| Support and incidents | Hours, channels, response targets, exclusions, escalation, update handling and end-of-support path. | Support policy, tickets and escalation history. |
| Marketing and references | Claims, customer permissions, relationship disclosures, review date and correction owner. | Source evidence, consent and approved published copy. |
Reproduce the product before representing it
A source repository or demo screen is not a successful customer rollout. Test the exact release and preserve evidence for normal sales, exceptions, closing and recovery before describing a capability to a shop.
Software rights are not partner authorization
Posnic POS is published under AGPL-3.0-only. The GNU license governs covered software rights and obligations. Downloading or redistributing the software does not by itself make an organization a Posnic partner, authorize Posnic trademarks, create a territory or make Posnic responsible for services sold by another business.
Applicants should review the exact license and obtain their own legal advice for modification, distribution, network use, notices and commercial arrangements. Any partner title, approved marketing language, commercial license or white-label permission must be stated separately in a signed written scope.
Keep an 18-record partner qualification file
The blank worksheet covers identity, service area, customer scope, product evidence, implementation, hardware, payment, tax, data, security, recovery, support, incidents, commercial terms, branding, references, exit and approval. A blank row is not an approval.
Download the qualification record
Do not place passwords, card data, unnecessary personal data or confidential customer material in this worksheet. Store sensitive evidence in an access-controlled system and reference it by an approved identifier.
Primary guidance for partner due diligence
Posnic release evidence
Start with the exact public release and pinned source used by the current product review.
GNU AGPL-3.0
Read the license text for covered software rights and obligations rather than treating open source as a partner credential.
NIST supply-chain guidance
NIST SP 1305 describes how acquirers and suppliers can define and communicate cybersecurity requirements.
PCI reseller boundary
PCI SSC distinguishes a product-only reseller from a reseller that provides ongoing services or accesses a customer's cardholder-data environment.
PCI merchant responsibility
Outsourcing payment processing does not remove the merchant's responsibility to oversee providers and understand shared duties.
FTC endorsement guidance
Customer claims and endorsements should be truthful, evidence-based and disclose material relationships where required.
Questions prospective partners ask
Does a partner inquiry create Posnic partner status?
No. An inquiry starts a qualification review. A written agreement is the only partner authorization, and it must define the approved scope and brand use.
Can anyone using the AGPL software call themselves an authorized Posnic partner?
No. Software-license rights and Posnic partner or trademark authorization are separate. Downloading, modifying or redistributing the software does not by itself create Posnic partner status or permission to use Posnic marks.
Does Posnic guarantee a territory, leads, margin or commission?
No public guarantee is made for territory, exclusivity, referrals, leads, margin, commission, certification, pricing or a support service level. Any agreed commercial term must be written.
Who owns payment-security responsibilities in a partner deployment?
The merchant remains responsible for its payment environment and third-party oversight. The parties must document whether a reseller has ongoing access or services, which payment duties apply to each party, and what evidence is required.
Can a partner publish a customer logo or success story?
Only with documented customer permission, accurate evidence and disclosure of any material relationship. A pilot, inquiry or software download is not a customer result.
Is white-label or commercial licensing included in the public partner program?
No white-label or commercial-license entitlement is promised on this page. A business may submit its requirements, but only a signed written scope establishes an offer or permission.