WEBVTT

00:00:00.250 --> 00:00:05.776
Welcome to the AgenticEcom Astro Admin guide to sync magento data. We're using the

00:00:05.823 --> 00:00:11.210
Sync Comms storefront to show the current controls. We'll review the workflow with previews, without

00:00:11.268 --> 00:00:13.439
saving changes to this live store.

00:00:14.489 --> 00:00:20.097
Save your content in Magento first, and refresh the relevant Magento bundle when that integration

00:00:20.189 --> 00:00:25.855
uses snapshots. Astro Admin copies the available data into the storefront. It

00:00:25.890 --> 00:00:31.486
cannot pull an edit that was never saved, or make an old Magento snapshot current by itself.

00:00:32.536 --> 00:00:38.225
Sync CMS pulls the content blocks and pages used by the storefront. After you run it

00:00:38.271 --> 00:00:43.844
on your store, review the reported blocks, pages and image URLs. If content

00:00:43.891 --> 00:00:49.371
is missing, check the Magento store assignment and active status, then the source snapshot.

00:00:49.986 --> 00:00:53.527
Our demonstration shows the current results without starting a sync.

00:00:54.577 --> 00:01:00.208
Sync Products copies product shells and category information. Review the total count

00:01:00.254 --> 00:01:05.943
and pagination rather than looking only at the first listed page. Verify product names and

00:01:06.001 --> 00:01:11.586
images, and separately check the live price, stock and add-to-cart flow. The

00:01:11.632 --> 00:01:15.986
displayed counts belong to Sync Comms and are not targets for another store.

00:01:17.036 --> 00:01:22.377
Sync Global Data updates store configuration, category navigation and related global

00:01:22.435 --> 00:01:28.054
metadata. Sync URL Rewrites updates the routing snapshot. Run

00:01:28.112 --> 00:01:33.313
the sync that matches your Magento changes, and both when a change affects both navigation and

00:01:33.429 --> 00:01:38.352
URLs. Test clean URLs and redirects after the data is pulled.

00:01:39.402 --> 00:01:44.963
On Sync URL Rewrites, inspect the entity-type summary and the current routing data.

00:01:45.486 --> 00:01:51.140
After a Magento URL-key change, verify the new address and any expected redirect

00:01:51.186 --> 00:01:56.771
from the old address. A successful data copy does not prove every route points to the intended

00:01:56.805 --> 00:01:57.932
destination.

00:01:58.982 --> 00:02:04.450
Schema Discovery refreshes the GraphQL fields the storefront knows about. Use it after an

00:02:04.497 --> 00:02:10.151
extension or schema change when your integration needs the new fields. It does not grant access

00:02:10.197 --> 00:02:15.375
to protected data. Finish with the appropriate prebuild and check representative pages on the

00:02:15.410 --> 00:02:16.397
storefront.

00:02:17.447 --> 00:02:22.776
To put this into practice, save and refresh the magento source, run the relevant astro

00:02:22.857 --> 00:02:28.511
sync, prebuild and verify data and urls. Test the complete result on your own

00:02:28.581 --> 00:02:34.258
staging storefront before publishing. You can follow the written Astro Admin guides at user guides

00:02:34.328 --> 00:02:36.580
dot AgenticEcom dot net.