Store listing draft — Cricket (EE-A-0003-A)

Prepared 2026-10-06 at the owner's request. Nothing is live, no price is set, nothing was created in either ERP. Product facts come only from cricket-product (Log 2026-10-06) and cricket-qr-page; instructions live at https://embeddedera.com/cricket/.

What was and was not done

• Done: listing copy and a hidden-draft creation script in the store repo (~/embeddedera-store, branch sandbox, uncommitted): scripts/configure-cricket.php, image themes/embeddedera/assets/cricket-ee-a-0003-a-hero.webp.
• Not done: the sandbox ERP record, the script run, the store build/tests and a preview. The permission classifier denied starting the sandbox ERP and even listing Docker containers. Nothing was worked around. Next step needs you (or a granted rule) to start the sandbox stack, then run wp eval-file scripts/configure-cricket.php and the ERP steps below.

Listing text (draft)

Title: Cricket — USB-A Sound Prank Device Short: Cricket is a USB-A sound prank device. Hide it, and after about an hour it starts making cricket, katydid or chaos sounds at random intervals. It looks like a flash drive, but it cannot store files. Instructions: embeddedera.com/cricket/ Long description, specs table, battery/shipping and "prank kindly" notes: in the script (single source). Facts used are only the verified list: power/control-only plug, stops on a standard 5 V USB-A wall charger, about 1 h start delay, 5 modes (cricket modes quiet below 13 C / 55 F), 4 speeds (15 min, 45 min default, 2 h, 4 h average gaps), red charging / green full, 3.7 V 100 mAh LiPo, piezo + vibration motor. No charge time, battery life or warranty claimed. SEO: title "Cricket USB-A Sound Prank Device | EmbeddedEra"; meta description in the script (_genesis_* keys; unverified against the installed SEO plugin until run). URL will be /product/ee-a-0003-a/ by the SKU policy. Image: Cricket008_labeled_hero.webp (CAD render of our own design, allowed by the owner; caption states it is a render). Alt: "Cricket USB-A sound prank device with a charcoal enclosure, cricket label, LED windows and an instructions QR code". The site's /media/cricket/ photos (disguise, internals, board) are available as extra images; not added. State: draft, catalog hidden, price empty, stock 0, _ee_listing_release=pending, no ERP mapping, category new "Devices".

Shipping and safety wording

Reused the batteries' approach (destination/service dependent, no blanket promise) but changed it for a device: the cell is installed, so it is lithium battery "contained in equipment", not a standalone cell. The plan note says USPS allows this with rules met; that is not verified (the USPS international page I read for the cells only prohibits batteries sent separately from equipment). Do not state carrier rules on the page until checked.

Proposed ERP record (apply on production only after approval)

Checked read-only on production: no Cricket parts exist; EE-A-0003 and EE-P-0003 were never used (the numbers were skipped, apparently reserved), so EE-A-0003-A is correct (SOP-001: class A, revision suffix A).

Field	Value
IPN / Name	EE-A-0003-A / Cricket
Description (SOP-002 v2.6)	CRICKET USB-A SOUND PRANK DEVICE 008 ASSEMBLED AND PACKED
Category / Units	Assemblies (pk 1) / pcs
Flags	Component ON, Assembly ON, Trackable ON, Testable ON (as Robot Cow), Purchaseable OFF, Salable OFF until you approve price and launch
Bare PCB	EE-P-0003-A "Cricket 008 PCB", BARE PCB CRICKET 008 2 LAYERS, category PCBs (pk 2), first BOM line
Image	the render (SOP-002 step 11 allows; not on the website so own-photos rule does not apply)

One part, not a separate kit. The boxed product is the same physical thing as the assembly; packaging lines (bag, labels, per the board packing pattern) go on EE-A-0003-A's own BOM, one listing, one stock pool. A kit is needed only for a real bundle. BOM caveat: the Cricket 008 schematic has no IPN fields, so erp-bom-import cannot load it. Engineering must add IPNs (SOP-008) first; then cell EE-C-0184, motor EE-C-0183, the printed shell and the packaging go on the BOM. Not created anywhere. Store mapping after creation: add registry entry EE-A-0003-A (multiplier 1, safety buffer your call) with the new production part id and bump registry_version; do not guess the id.

Decisions needed

1. Price, and whether quantity breaks apply (none proposed; per store-quantity-pricing one listing for any quantity). The plan's 3x landed cost has no BOM cost to work from yet.
2. Launch date; singles only (my default) versus a multi-pack as price breaks.
3. Shipping region and the lithium-in-equipment carrier rules; UN38.3 summary for the cell; FCC/RoHS statement.
4. Confirm every sold unit is flashed with rev008; units tested and in ERP stock (SOP-006, SOP-023).
5. Physical QR scan test of the engraved code on several phones.
6. Approve the "prank kindly" line and the "Devices" category; whether to add the shop photos.
7. Spanish/other copy, packaging contents and weight (none claimed).