pos-license

name	pos-license
title	Software & POS System License Agreement
description	Drafts Software and POS System License Agreements for proprietary software use between licensor and licensee. Covers license grants, financial terms, IP, PCI-DSS data security, SLAs, and termination. Use when drafting POS software licenses, SaaS subscriptions, franchise technology licenses, or software distribution agreements.
author	CaseMark
author_url	https://github.com/CaseMark/skills/tree/main/skills/legal/pos-license
license	Apache-2.0
version	0.1.0
execution_mode	open
jurisdiction	general
practice	contracts
language	en
tags	["agreement","drafting","transactional"]

Software & POS System License Agreement

Drafts a license agreement governing access, installation, and operation of proprietary software and POS system technology.

Prerequisites

Gather before drafting:

1. Parties — legal names, entity types, jurisdictions, bound affiliates
2. Software specs — deployment model (cloud/on-premises/hybrid), components, documentation, source vs. object code
3. Commercial terms — pricing model, payment schedule, renewal structure, user/location counts
4. Technical requirements — hardware integration, payment processing, inventory management, multi-location needs
5. Regulations — PCI-DSS, GDPR/CCPA applicability, state-specific licensing rules

Quick Start

1. Collect party and software details per Prerequisites
2. Draft each section below in order, flagging gaps with [NEEDS INPUT]
3. Mark jurisdiction-specific items with [JURISDICTION NOTE]
4. Run Checks before finalizing

Drafting Sections

1. Recitals & Definitions

• Identify parties with entity type, principal place of business, jurisdiction
• Establish licensor ownership context and licensee's business need
• Define all capitalized terms in a dedicated section or on first use

2. Grant of License

Parameter	Options
Exclusivity	Exclusive / Non-exclusive
Term	Perpetual / Fixed / Renewable
Scope	Internal use only / Third-party service permitted
Users	Named / Concurrent / Unlimited
Locations	Single-site / Multi-location / Geographic limits
Code access	Object code only / Source code included
Deployment	Cloud / On-premises / Hybrid
Updates	Included / Separate fee / Major vs. minor
Sublicensing	Prohibited / With consent / Affiliate carve-out

Explicitly restrict reverse engineering, decompilation, disassembly, and derivative works unless negotiated.

3. Financial Terms

• Fee structure — one-time / subscription / per-user / per-transaction / hybrid