SG365 CID Documentation
Detailed guidance for installing, configuring and operating the SG365 CID WooCommerce plugin. It connects PIDKey / CIDMS Confirmation ID requests with WooCommerce products, orders, allowances, logs, customer history and Business tokens.
Quick Start
5 stepsFollow these steps in order to connect the plugin with WooCommerce and publish the first customer CID form.
sg365-cid folder to /wp-content/plugins/, then activate SG365 CID from Plugins → Installed Plugins.[sg365_cid_form] to a normal WordPress page and save that page in the plugin settings where required.[sg365_cid_history], [sg365_cid_limits] or [sg365_cid_check_limit] in customer-only support areas.How the CID Workflow Operates
Order → CIDA normal customer request passes through verification, allowance checks, duplicate detection, API handling and logging.
1. Customer entitlement
The customer provides an order number or Business token. When email verification is enabled, the supplied email must match the expected entitlement.
2. Allowance check
The plugin checks the total allocation, previous usage, remaining requests and any configured expiry state.
3. Duplicate IID check
If the same verified order or email and Installation ID already produced a successful CID, the earlier result can be reused without reducing the remaining limit.
4. Primary and fallback API
The primary PIDKey / CIDMS endpoint is attempted first. A configured fallback can run before the request is recorded as failed.
5. Result and copy action
A successful Confirmation ID is shown immediately in the form with a copy-ready presentation.
6. Logged history
The request is connected with its customer, order or token, IID, result, status and operational metadata for later review.
WooCommerce Product Setup
Products & VariationsOnly qualifying products should create CID allowances. Configure the exact product or variation that should unlock customer requests.
01Enable CID limits on a simple product
02Enable CID limits on a variation
03Order allowance counters
04Thank-you and View Order messaging
05Auto-expire unused allowances
Settings Reference
Configuration MapThe available controls depend on the installed release and active Free, Premium or Business entitlement.
| Setting area | Purpose | Important behavior |
|---|---|---|
| API key | Connects requests with the configured PIDKey / CIDMS service. | Keep the key masked and available only to trusted administrators. |
| Primary endpoint | Main API destination for CID generation. | Test connectivity before publishing the customer form. |
| Fallback endpoint | Optional backup destination after primary failure. | A fallback attempt occurs before the request is finally marked failed. |
| API timeout | Limits how long the site waits for an endpoint response. | Do not set so high that customer requests appear frozen. |
| Rate limits | Controls repeated guest or logged-in requests. | Version 8.0 separates guest and logged-in request controls. |
| Math captcha | Reduces automated abuse. | Captcha visibility can be configured for guests or broader user groups. |
| Get CID page | Stores the customer-facing page URL. | Used by thank-you, order and optional email links. |
| Field visibility | Controls email and order/token fields. | Validation prevents the form from being left without a usable verification field. |
| Logs per page | Controls pagination on CID history. | Long histories use wider numbered pagination links. |
| Store failed attempts | Decides whether failed requests stay in logs. | Disable only when the operational team does not need failure history. |
| Customer email links | Adds allowance and Get CID links to selected WooCommerce emails. | This does not mean the generated CID itself is automatically emailed. |
| Auto-expiry | Expires unused allowances after a configured period. | Use a clear customer policy before activation. |
Shortcode Reference
Front EndPlace only the tools customers need. Keep history and allowance screens inside authenticated or customer-only areas where appropriate.
[sg365_cid_form][sg365_cid_history][sg365_cid_limits][sg365_cid_check_limit]Complete Admin Page Guide
Every ModuleThe major plugin screens are grouped below with their practical purpose and operational boundaries.
01Dashboard
- Reviews CID successes, errors, success rate and request trends.
- Shows license status and top Business tokens or WooCommerce orders where entitled.
- Provides quick instructions and shortcode references.
- Use the dashboard for monitoring, not as a replacement for detailed log investigation.
02Admin Get CID
- Premium administrator workflow for direct CID generation.
- Can optionally look up a WooCommerce order and consume an available allowance.
- Can confirm when an order does not have CID capacity.
- Later versions include Installation ID and image-assisted interface choices where available.
- Manual requests remain logged as administrator actions.
03CID Logs
- Search by customer, order, token or Installation ID.
- Review successful and failed states with clearer badges.
- Use configured rows-per-page pagination.
- Export through TXT or CSV controls where included.
- Delete older records through the available retention tools.
- Choose whether failed attempts should be stored.
04Settings
05CID Allowance Adjuster
- Business-only order allowance tool.
- Revoke all remaining requests or subtract a custom number.
- Version 6.5.1 records the latest five revoke actions with user and date attribution.
- Use only after confirming the order and customer policy.
06User Manager
- Administrator-controlled per-user access.
- Assign hidden, read or write access by plugin page.
- Administrators are not shown as ordinary managed users.
- Use least-privilege access for support staff.
07Get CID Form Styles
- Select Classic, Modern or available preset layouts.
- Configure button colors, backgrounds, fonts, placeholders, alignment and icon or emoji choices.
- Control visible verification fields and captcha presentation.
- Version 8.0 separates styling from request-control settings more clearly.
08Tools and data actions
- Provides maintenance and future operational utilities according to the installed release.
- A gated wipe action can remove plugin logs, tokens and settings after license-key confirmation.
- Back up the WordPress database before destructive actions.
Business Token Documentation
Business PlanBusiness tokens give selected customers a reusable entitlement that does not depend on entering a normal order number for every request.
Create a token
Enter a token label, customer name, email, request limit and optional expiry. The success popup provides token details and copy-ready sharing text.
Manage usage
Review used and remaining requests, active or used state, customer information and request history.
Refill capacity
Version 8.0 adds clearer token refill controls. Confirm the intended new limit before applying it.
Recently Deleted
The recycle bin keeps the most recent five deleted tokens and trims older recovery entries when new deletions occur.
Restore a token
Use the Recently Deleted modal and restore action when the token was removed accidentally and is still eligible for recovery.
Customer verification
The customer selects token-based access, supplies the token and email when required, then submits the Installation ID.
License Guard and Entitlements
Premium AccessThe license system validates the SG365 CID product, activated domain, plan, status and expiry before keeping paid capabilities available.
Verify and activate
AJAX verification and activation provide loading feedback and refresh the premium feature state after a successful response.
Masked key display
The active key is masked in the admin interface while plan, status, expiry and last-check information remain visible.
Supported paid states
The interface can identify Premium, Subscription and Business plan types according to the verification response.
Scheduled checks
The plugin rechecks license state automatically at least weekly according to the supplied description.
Invalid state reaction
Pending, suspended, deleted, expired or domain-reset states can disable Premium and Business capabilities.
Renewal flow
Renewed licenses are designed to reactivate entitled capabilities and refresh expiry messaging more smoothly.
Security, Privacy and Operational Safety
ControlsThe documentation supplied for this plugin describes a controlled, logged request workflow. It does not claim that an external API can never fail.
Secure AJAX workflow
Customer and administrator actions should pass through the plugin's validation and authorization logic rather than direct unprotected requests.
Captcha and rate limiting
Use math captcha and realistic request limits to reduce automated abuse without blocking legitimate customers.
Duplicate IID reuse
A successful duplicate match avoids another API request and does not consume a second allowance.
Least-privilege staff access
User Manager can restrict individual pages to hidden, read or write access.
Responsive privacy choices
The allowance table removed the last-generated CID column in later releases, and customer history can display masked values.
License enforcement
Scheduled verification helps prevent expired or suspended paid capabilities from remaining active indefinitely.
Troubleshooting
Common Fixes01The customer has no CID allowance
- Confirm the purchased product or variation is CID-enabled.
- Check that the relevant order contains the qualifying item and quantity.
- Review order metadata and use automatic allowance re-sync where available.
- Confirm the allowance has not expired or already been consumed.
02The primary endpoint returns an error
- Confirm the API key and primary endpoint.
- Review timeout configuration.
- Confirm whether the fallback endpoint is configured and reachable.
- Review CID Logs for the recorded status instead of repeatedly resubmitting.
03Captcha expired or the customer entered the wrong answer
04A duplicate Installation ID appears
05Premium pages are visible but locked
- Open the License page and verify the active key.
- Check plan, domain, status and expiry.
- Refresh the license state after renewal.
- Remember that Business token and Allowance Adjuster access requires the appropriate entitlement.