Athenian Google Sheets App Script Integration
Overview
Product overview
WooCommerce becomes operationally slow when teams need to manage large amounts of product, pricing, vendor, and order data by hand. Product descriptions live in one interface, dimensions in another, vendor offers inside custom meta, order updates in admin screens, and media management somewhere else. Bulk edits often depend on imports that are hard to validate, hard to repeat, and easy to break.
AWGS solves that by creating a secure, repeatable bridge between Google Sheets and WooCommerce. It exposes purpose-built GraphQL queries and mutations for round-trip data sync, authenticates spreadsheet-driven actions with Athenian HMAC, and gives teams structured sheet workflows for products, vendors, vendor offers, orders, and media. The result is a spreadsheet-native control surface for WooCommerce that is faster to operate and safer to extend.
Use cases
- Operations reporting
- Catalog exports
- Order synchronization
- Google Sheets workflows
Developer
Developer starting point
This baseline documents the Google Sheets integration architecture. It does not claim that a live Apps Script request, sheet write, order export, or synchronized operational report has been exercised.
Ecosystem integration story
WooCommerce
AWGS works directly against WooCommerce products, variations, orders, pricing fields, dimensions, and metadata. It preserves WooCommerce as the transactional system while making operational changes easier to stage and execute from spreadsheets.
WPGraphQL and WooGraphQL
AWGS depends on a GraphQL-based integration model instead of a legacy import-only model. It adds custom queries and mutations where needed, uses GraphQL schema discovery to adapt safely, and gives spreadsheet automation a modern API surface for both export and update workflows.
Google Sheets and Apps Script
Google Sheets is the working environment for AWGS. Apps Script provides the user-facing menus, configuration, import/sync actions, dry-run flows, and row-level batching behavior that allow non-developer teams to work in a familiar tool while still interacting with WooCommerce safely.
Athenian Platform Kernel
When Athenian Platform Kernel is present, AWGS can register managed field definitions into the broader Athenian schema layer. That makes the plug-in easier to discover, validate, and coordinate inside a larger Athenian platform deployment.
Vendor-aware Athenian commerce workflows
AWGS aligns especially well with Athenian stores that use vendor-specific offers, tiered pricing data, and richer operational metadata. It does not replace vendor or pricing logic. It makes that logic manageable at scale through a spreadsheet-native workflow.
Install
- Reviewed source folder: athenian-woocommerce-google-sheets-integration
- Plugin version reviewed: 0.7.0
- Local source inventory: 49 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-woocommerce-google-sheets-integration at baseline/devdocs-0.7.0-20261006h / 3b2c957bff8ea0020d342848bf06fa30ed702660.
- WordPress, WooCommerce, Google Sheets/Apps Script, and configured transport credentials.
- External sheet writes, sync freshness, credentials, order data, and downstream spreadsheet effects require separate target verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem AWGS solves — see the linked technical reference excerpt.
- What AWGS does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Operations-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 0
- Static action/filter hooks detected in local PHP source: 20
- REST route registrations detected in local PHP source: 7
Shortcodes
- No static add_shortcode registrations were detected by the baseline scanner.
REST Endpoints
- /entities/(?P<entity>[a-z0-9_-]+)/batch — includes/GenericSync.php
- /entities/(?P<entity>[a-z0-9_-]+)/delete — includes/GenericSync.php
- /entities/(?P<entity>[a-z0-9_-]+) — includes/GenericSync.php
- /prices/batch — includes/Rest.php
- /products/export — includes/Rest.php
- /schema — includes/GenericSync.php
- /validate — includes/GenericSync.php
Hooks
- admin_enqueue_scripts — includes/SiteSchemaStudio.php
- admin_init — includes/Admin.php
- admin_menu — includes/Admin.php
- admin_menu — includes/SiteSchemaStudio.php
- admin_post_awgs_activate_site_schema — includes/SiteSchemaStudio.php
- admin_post_awgs_delete_site_schema — includes/SiteSchemaStudio.php
- admin_post_awgs_export_apps_script — includes/PackageExporter.php
- admin_post_awgs_export_schema_json — includes/PackageExporter.php
- admin_post_awgs_export_schema_xlsx — includes/PackageExporter.php
- admin_post_awgs_generate_site_schema — includes/SiteSchemaStudio.php
- graphql_register_types — includes/GraphQL.php
- graphql_register_types — includes/GraphQLSyncEntities.php
- graphql_request_data — includes/GraphQL.php
- init — includes/GraphQL.php
- init — includes/GraphQLSyncEntities.php
- init — includes/Plugin.php
- init — includes/SiteSchemaStudio.php
- plugins_loaded — athenian-woocommerce-google-sheets-integration.php
- rest_api_init — includes/GenericSync.php
- rest_api_init — includes/Rest.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 7172ea2f3f10a07011107cdb12cede03b930ef1c294ee47e3377c88687806afc
- Repository URL: https://github.com/Athenian-Brands/athenian-woocommerce-google-sheets-integration
- Repository reference: baseline/devdocs-0.7.0-20261006h
- Repository commit: 3b2c957bff8ea0020d342848bf06fa30ed702660
Source files include: CHANGELOG.md, README.md, app-script.zip, app-script/Main.gs, app-script/Media.gs, app-script/Orders.gs, app-script/Products.gs, app-script/SchemaSync.gs, app-script/VendorOffers.gs, app-script/Vendors.gs, assets/css/admin.css, assets/js/admin.js, assets/js/schema-studio.js, athenian-google-sheets-intigration-icon.png, athenian-woocommerce-google-sheets-integration.php, dist/athenian-woocommerce-google-sheets-integration-0.6.0-deploy.zip, dist/athenian-woocommerce-google-sheets-integration-0.6.1-deploy.zip, dist/athenian-woocommerce-google-sheets-integration-0.7.0-deploy.zip, dist/gigcourses-academy-site/gigcourses-academy-site-apps-script.zip, dist/gigcourses-academy-site/gigcourses-academy-site-schema.json, dist/gigcourses-academy-site/gigcourses-academy-site-template.xlsx, dist/gigcoursescom-0.7.0/gigcoursescom-apps-script.zip, dist/gigcoursescom-0.7.0/gigcoursescom-schema.json, dist/gigcoursescom-0.7.0/gigcoursescom-template.xlsx, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/awgs-marketing-document.md, docs/awgs-site-profile-v1.schema.json, …
Troubleshooting
This baseline documents the Google Sheets integration architecture. It does not claim that a live Apps Script request, sheet write, order export, or synchronized operational report has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.